Many small updates, enhancements, bug fixes!!! We've been saving them up!! Here
they are!! Don't wait!!
Thanks mr. mazda for many issue finds, and suggestions.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. Due to unfixable rpm slowdowns, removed package counts for default output for
rpm based systems. We were seeing delays of up to 30+ seconds just to list the
rpm package count, which is absurd, even after the rpm optimizations inxi
already runs. To allow rpm users to get excluded by default for rpm package list
counts, added --pkg flag plus a short message telling them to use that flag to
get the installed package count if they want it.
Changes like this are very unfortunate, but in 2021 for a package manager at
times to require over 30 seconds to generate a trivial installed package list is
just not acceptable. One of the reasons this release was delayed was this was
not an easy decision to make, it's very rare support for a feature is removed
for specific tools due to how badly the tools may perform. Note that whatever
higher level tool is used, like dnf, zypp, it's still the same speed, they all
appear to use the same core engine.
Basically this decision was forced since either inxi looks really bad and slow,
when it's not, or the actual cause was removed from default outputs.
--------------------------------------------------------------------------------
BUGS:
1. Small bug in nfs blacklist for disk used led to nfs used being added, which
leads to silly used percents. This is corrected.
2. If ram vendor ID failed, inxi would delete the part number. Oops. This was
related to the Mushkin failures.
3. Close to a bug, though not one internally, but to users would appear as one:
ZFS does not act as expected, zpool list did not in fact return the pool size,
which I had always assumed to be the case, but in a very strange decision, does
return something very close to the pool size for mirrors, but NOT for z1 or z2
pools, then it returns the total size of the drives that make up the pool. To
call this strange behavior would be an understatement. The fix was to modify the
logic to use zfs list instead to get the size data. This also makes the drive
total report far more accurate, since it lists usable space now for ZFS as was
always intended. The cause of this was simply that I'd always had access to zfs
mirrors, not z1 or z2 arrays.
--------------------------------------------------------------------------------
FIXES:
1. OpenSuse and maybe others use kdm3 for Trinity, not kdm, so dm was failing.
2. Going along with fix 1, made kde version detection more robust so may catch
more fringe / corner cases for kde desktops. These were mainly added to correct
Trinity desktop version detections.
3. Mushkin ram vendor ID was failing, that is or should be corrected.
4. Added in /dev/disk/by-id handlers for zpool components, there are several
variants, wwn-, pci-, scsi-, ata-, but they all map to the real /dev drive IDs.
Failure to unmap these led to failing to match components and get size info
etc for zfs.
5. See DOCUMENTATION: 2, language changes for weather feature abuse.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo
types. Not sure how that one was missed, but there it is. This should tighten
repo reports for dnf/yum/zypp types.
2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for:
penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2.
3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
since xfwm can run in compositing or non compositing mode. But should show
since many users use compositing mode now.
4. Added OpenMediaVault distro ID and systembase handlers.
5. Going along with zfs bug fix 3, using zfs list data for free, size,
allocated. Trying to understand how zfs developers actually thought about this
is nearly impossible so just used what seems to correspond to reality most.
Also shows raw values for zfs data in RAID along with regular ones to make
clear which is which value.
6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
Both vendors finally released some new CPUs and the data became available,
which doesn't always happen quickly.
7. A bunch of new disk vendors and vendor IDs added. Never stops, like the
sands of time, like the ocean waves, like the scuttling crabs scrounding around
in the seaweed in the foam where the outgoing wave left its mark...
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added leftwm keybindinigs to inxi-data.txt desktop/wm section. Updated more
wm in that section as well, and list more info on wms for future reference etc.
Also reorganized and more more readable wm section.
2. Help/Man now make more clear that automated requests or excessive use of the
inxi weather feature are not under any circumstance permitted. There had been
some ambiguity and lack of clarity about what abuse is, now it should be more
clear.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Refactored uptime parser logic, the code and regex was just getting too
messy and difficult to work with and debug, now it works similar to how the
revised BSD parsers run, the regex are pulled apart and made more granular so
a small syntax change ideally won't break the detections as easily.
2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
time I notice that almost invariably stuff done to save lines of code makes
code harder to read as the feature expands, so it's generally worth just
unravelling it so it all stacks and is easy to scan/read. Also removed extra
white space in parens, which is something I'm leaning more towards but it's
not worth fixing all at once so it's just done where it's noticed.
That's using:
if ( /test/ ){
rather than:
if (/test){
I believe using more white space helped with Perl comprehension in the
intermediate stages, but is not required anymore and just looks like extra
whitespace now.
2021-07-12 02:32:13 +00:00
|
|
|
.\" inxi.1 - manpage for inxi system information tool
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.\" Copyright (C) 2023 Harald Hope
|
Many small updates, enhancements, bug fixes!!! We've been saving them up!! Here
they are!! Don't wait!!
Thanks mr. mazda for many issue finds, and suggestions.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. Due to unfixable rpm slowdowns, removed package counts for default output for
rpm based systems. We were seeing delays of up to 30+ seconds just to list the
rpm package count, which is absurd, even after the rpm optimizations inxi
already runs. To allow rpm users to get excluded by default for rpm package list
counts, added --pkg flag plus a short message telling them to use that flag to
get the installed package count if they want it.
Changes like this are very unfortunate, but in 2021 for a package manager at
times to require over 30 seconds to generate a trivial installed package list is
just not acceptable. One of the reasons this release was delayed was this was
not an easy decision to make, it's very rare support for a feature is removed
for specific tools due to how badly the tools may perform. Note that whatever
higher level tool is used, like dnf, zypp, it's still the same speed, they all
appear to use the same core engine.
Basically this decision was forced since either inxi looks really bad and slow,
when it's not, or the actual cause was removed from default outputs.
--------------------------------------------------------------------------------
BUGS:
1. Small bug in nfs blacklist for disk used led to nfs used being added, which
leads to silly used percents. This is corrected.
2. If ram vendor ID failed, inxi would delete the part number. Oops. This was
related to the Mushkin failures.
3. Close to a bug, though not one internally, but to users would appear as one:
ZFS does not act as expected, zpool list did not in fact return the pool size,
which I had always assumed to be the case, but in a very strange decision, does
return something very close to the pool size for mirrors, but NOT for z1 or z2
pools, then it returns the total size of the drives that make up the pool. To
call this strange behavior would be an understatement. The fix was to modify the
logic to use zfs list instead to get the size data. This also makes the drive
total report far more accurate, since it lists usable space now for ZFS as was
always intended. The cause of this was simply that I'd always had access to zfs
mirrors, not z1 or z2 arrays.
--------------------------------------------------------------------------------
FIXES:
1. OpenSuse and maybe others use kdm3 for Trinity, not kdm, so dm was failing.
2. Going along with fix 1, made kde version detection more robust so may catch
more fringe / corner cases for kde desktops. These were mainly added to correct
Trinity desktop version detections.
3. Mushkin ram vendor ID was failing, that is or should be corrected.
4. Added in /dev/disk/by-id handlers for zpool components, there are several
variants, wwn-, pci-, scsi-, ata-, but they all map to the real /dev drive IDs.
Failure to unmap these led to failing to match components and get size info
etc for zfs.
5. See DOCUMENTATION: 2, language changes for weather feature abuse.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo
types. Not sure how that one was missed, but there it is. This should tighten
repo reports for dnf/yum/zypp types.
2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for:
penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2.
3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
since xfwm can run in compositing or non compositing mode. But should show
since many users use compositing mode now.
4. Added OpenMediaVault distro ID and systembase handlers.
5. Going along with zfs bug fix 3, using zfs list data for free, size,
allocated. Trying to understand how zfs developers actually thought about this
is nearly impossible so just used what seems to correspond to reality most.
Also shows raw values for zfs data in RAID along with regular ones to make
clear which is which value.
6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
Both vendors finally released some new CPUs and the data became available,
which doesn't always happen quickly.
7. A bunch of new disk vendors and vendor IDs added. Never stops, like the
sands of time, like the ocean waves, like the scuttling crabs scrounding around
in the seaweed in the foam where the outgoing wave left its mark...
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added leftwm keybindinigs to inxi-data.txt desktop/wm section. Updated more
wm in that section as well, and list more info on wms for future reference etc.
Also reorganized and more more readable wm section.
2. Help/Man now make more clear that automated requests or excessive use of the
inxi weather feature are not under any circumstance permitted. There had been
some ambiguity and lack of clarity about what abuse is, now it should be more
clear.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Refactored uptime parser logic, the code and regex was just getting too
messy and difficult to work with and debug, now it works similar to how the
revised BSD parsers run, the regex are pulled apart and made more granular so
a small syntax change ideally won't break the detections as easily.
2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
time I notice that almost invariably stuff done to save lines of code makes
code harder to read as the feature expands, so it's generally worth just
unravelling it so it all stacks and is easy to scan/read. Also removed extra
white space in parens, which is something I'm leaning more towards but it's
not worth fixing all at once so it's just done where it's noticed.
That's using:
if ( /test/ ){
rather than:
if (/test){
I believe using more white space helped with Perl comprehension in the
intermediate stages, but is not required anymore and just looks like extra
whitespace now.
2021-07-12 02:32:13 +00:00
|
|
|
.\"
|
|
|
|
|
.\" This program is free software; you can redistribute it and/or modify
|
|
|
|
|
.\" it under the terms of the GNU General Public License as published by
|
|
|
|
|
.\" the Free Software Foundation; either version 3 of the License, or
|
|
|
|
|
.\" (at your option) any later version.
|
|
|
|
|
.\"
|
|
|
|
|
.\" This program is distributed in the hope that it will be useful,
|
|
|
|
|
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
.\" GNU General Public License for more details.
|
|
|
|
|
.\"
|
|
|
|
|
.\" You should have received a copy of the GNU General Public License along
|
|
|
|
|
.\" with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
|
|
|
|
.\"
|
2023-09-18 00:42:36 +00:00
|
|
|
.TH INXI 1 "2023\-09\-17" "inxi" "inxi manual"
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH NAME
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
inxi \- Command line system information script for console and IRC
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH SYNOPSIS
|
New version, new man. Bug fixes. BSD fixes.
Bugs fixed:
1. CPU: MT/HT was wrong for old xeon, made mt detection more robust and hopefully
more reliable, removed all explicit b_xeon based tests.
2. fixed /dev/mapper glitch, that make /dev/mapper links fail to get id'ed.
3. openbsd: fixed memory handler; fixed cpu flags, fixed partitions handling.
4. freebsd: fixed similar partition bugs, these were caused by the darwin patch.
5. man page: fixed top synopis syntax, thanks ESR.
6. partitions fs: fixed possible failures with lsblk fs. lsblk: added debuggers
so we can track down this failure in the future.
7. added sshfs filter for disk used output, note, there is a possible syntax for
remote fs that isn't handled: AAA:BBB that is, no :/, only the :. This makes
explicit detection of still unknown remote fs very difficult since : is a legal
nix filename character.
2018-04-19 02:35:49 +00:00
|
|
|
\fBinxi\fR
|
2016-10-29 22:25:55 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBinxi\fR [\fB\-AbBCdDEfFGhiIjJlLmMnNopPrRsSuUVwyYzZ\fR]
|
2016-10-29 22:25:55 +00:00
|
|
|
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\fBinxi\fR [\fB\-c -NUMBER\fR]
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
[\fB\-\-sensors\-exclude SENSORS\fR] [\fB\-\-sensors\-use SENSORS\fR]
|
2020-11-11 23:45:10 +00:00
|
|
|
[\fB\-t\fR [\fBc\fR|\fBm\fR|\fBcm\fR|\fBmc\fR][\fBNUMBER\fR]]
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
[\fB\-v NUMBER\fR] [\fB\-W LOCATION\fR]
|
2018-05-21 22:11:04 +00:00
|
|
|
[\fB\-\-weather\-unit\fR {\fBm\fR|\fBi\fR|\fBmi\fR|\fBim\fR}] [\fB\-y WIDTH\fR]
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
\fBinxi\fR [\fB\-\-edid\fR] [\fB\-\-memory\-modules\fR]
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
[\fB\-\-memory\-short\fR] [\fB\-\-recommends\fR] [\fB\-\-sensors\-default\fR]
|
|
|
|
|
[\fB\-\-slots\fR]
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
\fBinxi\fB [\fB\-x\fR|\fB\-xx\fR|\fB\-xxx\fR|\fB\-a\fR] \fB\-OPTION(s)\fR
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
All short form options have long form variants \- see below for these and more
|
|
|
|
|
advanced options.
|
2018-03-26 22:03:15 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH DESCRIPTION
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBinxi\fR is a command line system information script built for console and
|
|
|
|
|
IRC. It is also used a debugging tool for forum technical support to quickly
|
|
|
|
|
ascertain users' system configurations and hardware. inxi shows system
|
|
|
|
|
hardware, CPU, drivers, Xorg, Desktop, Kernel, gcc version(s), Processes, RAM
|
|
|
|
|
usage, and a wide variety of other useful information.
|
2018-04-06 22:52:08 +00:00
|
|
|
|
|
|
|
|
\fBinxi\fR output varies depending on whether it is being used on CLI or IRC,
|
|
|
|
|
with some default filters and color options applied only for IRC use.
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
Script colors can be turned off if desired with \fB\-c 0\fR, or changed
|
|
|
|
|
using the \fB\-c\fR color options listed in the STANDARD OPTIONS section below.
|
2018-03-26 22:03:15 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH PRIVACY AND SECURITY
|
2018-04-06 22:52:08 +00:00
|
|
|
In order to maintain basic privacy and security, inxi used on IRC automatically
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
filters out your network device MAC address, WAN and LAN IP, your \fB/home\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
username directory in partitions, and a few other items.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
Because inxi is often used on forums for support, you can also trigger this
|
|
|
|
|
filtering with the \fB\-z\fR option (\fB\-Fz\fR, for example). To override
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
the IRC filter, you can use the \fB\-Z\fR option. This can be useful in
|
|
|
|
|
debugging network connection issues online in a private chat, for example.
|
2018-03-26 22:03:15 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
.SH TABLE OF CONTENTS
|
|
|
|
|
This man page is pretty long and information packed. It is divided into the
|
|
|
|
|
following sections:
|
|
|
|
|
|
|
|
|
|
* \fBUSING OPTIONS\fR How to use the command line options.
|
|
|
|
|
|
|
|
|
|
* \fBSTANDARD OPTIONS\fR Primary data types trigger items.
|
|
|
|
|
|
|
|
|
|
* \fBFILTER OPTIONS\fR Apply a variety of output filters.
|
|
|
|
|
|
|
|
|
|
* \fBOUTPUT CONTROL OPTIONS\fR Change default colors, widths, heights, output
|
|
|
|
|
types, etc.
|
|
|
|
|
|
|
|
|
|
* \fBEXTRA DATA OPTIONS\fR What \fB\-x\fR, \fB\-xx\fR, and \fB\-xxx\fR add to
|
|
|
|
|
the output per primary data type.
|
|
|
|
|
|
|
|
|
|
* \fBADMIN EXTRA DATA OPTIONS\fR What \fB\-a\fR adds to the output per primary
|
|
|
|
|
data type. These have a lot of information because this is advanced admin data,
|
|
|
|
|
which are not always intuitive or easy to understand.
|
|
|
|
|
|
|
|
|
|
* \fBADVANCED OPTIONS\fR Modify behavior or choice of data sources, and other
|
|
|
|
|
advanced switches.
|
|
|
|
|
|
|
|
|
|
* \fBDEBUGGING OPTIONS\fR For development use mainly, or contributing datasets
|
|
|
|
|
to the project.
|
|
|
|
|
|
|
|
|
|
* \fBDEBUGGING OPTIONS TO DEBUG DEBUGGER FAILURES\fR Only for advanced users,
|
|
|
|
|
sometimes something will hang the debuggers, this shows you various ways to get
|
|
|
|
|
around those failures.
|
|
|
|
|
|
|
|
|
|
* \fBSUPPORTED IRC CLIENTS\fR List of known good IRC clients. Not checked often,
|
|
|
|
|
let us know if something is not working.
|
|
|
|
|
|
|
|
|
|
* \fBRUNNING IN IRC CLIENT\fR How to run inxi in various IRC clients.
|
|
|
|
|
|
|
|
|
|
* \fBCONFIGURATION FILE\fR Configuration file locations and priority in using.
|
|
|
|
|
|
|
|
|
|
* \fBCONFIGURATION OPTIONS\fR Most of the commonly used configuration options,
|
|
|
|
|
along with sample values.
|
|
|
|
|
|
|
|
|
|
* \fBBUGS\fR How and where to report bugs.
|
|
|
|
|
|
|
|
|
|
* \fBHOMEPAGE\fR, \fBAUTHOR AND CONTRIBUTORS TO CODE\fR, \fBSPECIAL THANKS TO
|
|
|
|
|
THE FOLLOWING\fR These are self explanitory.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH USING OPTIONS
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Options can be combined if they do not conflict. You can either group the
|
|
|
|
|
letters together or separate them.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
Letters with numbers can have no gap or a gap at your discretion, except when
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
using \fB \-t\fR. Note that if you use an option that requires an additional
|
|
|
|
|
argument, that must be last in the short form group of options. Otherwise
|
|
|
|
|
you can use those separately as well.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
For example:
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
\fBinxi \-AG\fR | \fBinxi \-A \-G\fR | \fBinxi \-b\fR | \fBinxi \-c10\fR
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
| \fBinxi \-FxxzJy90\fR | \fBinxi \-bay\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
Note that all the short form options have long form equivalents, which are
|
2018-04-06 22:52:08 +00:00
|
|
|
listed below. However, usually the short form is used in examples in order to
|
2018-03-31 03:12:25 +00:00
|
|
|
keep things simple.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.SH STANDARD OPTIONS
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-A \fR, \fB\-\-audio\fR
|
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 21:48:52 +00:00
|
|
|
Show Audio/sound device(s) information, including device driver. Shows active
|
|
|
|
|
sound API(s) and sound server(s).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
Supported APIs: ALSA, OSS, sndio. Supported servers: aRts (artsd), Enlightened
|
|
|
|
|
Sound Daemon (esound, esd), JACK, NAS (Network Audio System, nasd), PipeWire,
|
|
|
|
|
PulseAudio, RoarAudio, sndiod.
|
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 21:48:52 +00:00
|
|
|
|
2023-03-28 21:54:49 +00:00
|
|
|
Use \fB\-Ax\fR to show all sound APIs/servers detected, including inactive,
|
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 21:48:52 +00:00
|
|
|
\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
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-b \fR, \fB\-\-basic\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
Show basic output, short form. Same as: \fBinxi \-v 2\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-B \fR, \fB\-\-battery\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show system battery (\fBID\-x\fR) data, charge, condition, plus extra
|
|
|
|
|
information (if battery present). Uses \fB/sys\fR or, for BSDs without systctl
|
|
|
|
|
battery data, use \fB\-\-dmidecode\fR to force its use. \fBdmidecode\fR does
|
|
|
|
|
not have very much information, and none about current battery
|
|
|
|
|
state/charge/voltage. Supports multiple batteries when using \fB/sys\fR or
|
|
|
|
|
\fBsysctl\fR data.
|
|
|
|
|
|
|
|
|
|
Note that for \fBcharge:\fR, the output shows the current charge, as well as
|
|
|
|
|
its value as a percentage of the available capacity, which can be less than
|
|
|
|
|
the original design capacity. In the following example, the actual current
|
|
|
|
|
available capacity of the battery is \fB22.2 Wh\fR.
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBcharge: 20.1 Wh (95.4%)\fR
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
The \fBcondition:\fR item shows the remaining available capacity / original
|
|
|
|
|
design capacity, and then this figure as a percentage of original capacity
|
|
|
|
|
available in the battery.
|
2018-03-31 03:12:25 +00:00
|
|
|
|
|
|
|
|
\fBcondition: 22.2/36.4 Wh (61%)\fR
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
With \fB\-x\fR, or if voltage difference is critical, \fBvolts:\fR item shows
|
|
|
|
|
the current voltage, and the \fBmin:\fR voltage. Note that if the current is
|
|
|
|
|
below the minimum listed the battery is essentially dead and will not charge.
|
|
|
|
|
Test that to confirm, but that's technically how it's supposed to work.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
|
|
|
|
\fBvolts: 12.0 min: 11.4\fR
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
With \fB\-x\fR shows attached \fBDevice\-x\fR information (mouse, keyboard,
|
|
|
|
|
etc.) if they are battery powered.
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-bluetooth\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-E\fR.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-c \fR, \fB\-\-color\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fBOUTPUT CONTROL OPTIONS\fR.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-config\fR, \fB\-\-configuration\fR
|
|
|
|
|
Show active configuration values, by file, and exit.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-C \fR, \fB\-\-cpu\fR
|
|
|
|
|
Show full CPU output (if each item available): basic CPU topology, model, type,
|
|
|
|
|
L2 cache, average speed of all cores (if > 1 core, otherwise speed of the core),
|
|
|
|
|
min/max speeds for CPU, and per CPU clock speed. More data available with
|
|
|
|
|
\fB\-x\fR, \fB\-xxx\fR, and \fB\-a\fR options.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Explanation of CPU type (\fBtype: MT MCP\fR) abbreviations:
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
* \fBAMCP\fR \- Asymmetric Multi Core Processor. More than 1 core per CPU, and
|
|
|
|
|
more than one core type (single and multithreaded cores in the same CPU).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
* \fBAMP\fR \- Asymmetric Multi Processing (more than 1 physical CPU, but not
|
|
|
|
|
identical in terms of core counts or min/max speeds).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
* \fBMT\fR \- Multi/Hyper Threaded CPU (more than 1 thread per core, previously
|
|
|
|
|
\fBHT\fR).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
* \fBMST\fR \- Multi and Single Threaded CPU (a CPU with both Single and Multi
|
|
|
|
|
Threaded cores).
|
2017-12-07 19:22:59 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
* \fBMCM\fR \- Multi Chip Model (more than 1 die per CPU).
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
* \fBMCP\fR \- Multi Core Processor (more than 1 core per CPU).
|
2017-12-07 19:22:59 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
* \fBSMP\fR \- Symmetric Multi Processing (more than 1 physical CPU).
|
2017-12-07 19:22:59 +00:00
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
* \fBUP\fR \- Uni (single core) Processor.
|
2017-12-07 19:22:59 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Note that \fBmin/max:\fR speeds are not necessarily true in cases of
|
|
|
|
|
overclocked CPUs or CPUs in turbo/boost mode. See \fB\-Ca\fR for alternate
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBbase/boost:\fR speed data, more granular cache data, and more.
|
|
|
|
|
|
|
|
|
|
Sample:
|
|
|
|
|
.nf
|
|
|
|
|
\fBCPU:
|
|
|
|
|
Info: 2x 8\-core model: Intel Xeon E5\-2620 v4 bits: 64 type: MT MCP SMP
|
|
|
|
|
cache: L2: 2x 2 MiB (4 MiB)
|
|
|
|
|
Speed (MHz): avg: 1601 min/max: 1200/3000 cores: 1: 1280 2: 1595 3: 1416
|
|
|
|
|
... 32: 1634\fR
|
|
|
|
|
.fi
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-d \fR, \fB\-\-disk\-full\fR,\fB\-\-optical\fR
|
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 18:59:56 +00:00
|
|
|
Show optical drive data as well as \fB\-D\fR HDD/SSD drive data. With \fB\-x\fR,
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
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
|
|
|
|
|
data. \fB\-xx\fR adds a few more features.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-D \fR, \fB\-\-disk\fR
|
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 18:59:56 +00:00
|
|
|
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
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
percentages since inxi has no access to the used amount.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
If the system has RAID or other logical storage, and if inxi can determine
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
the size of those vs their components, you will see the storage total raw and
|
|
|
|
|
usable sizes, plus the percent used of the usable size. The no argument short
|
|
|
|
|
form of inxi will show only the usable (or total if no usable) and used
|
|
|
|
|
percent. If there is no logical storage detected, only \fBtotal:\fR and
|
|
|
|
|
\fBused:\fR will show. Sample (with RAID logical size calculated):
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBLocal Storage: total: raw: 5.49 TiB usable: 2.80 TiB used: 1.35 TiB
|
|
|
|
|
(48.3%)\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
Without logical storage detected:
|
|
|
|
|
|
|
|
|
|
\fBLocal Storage: total: 2.89 TiB used: 1.51 TiB (52.3%)\fR
|
New version, new tarball. New features, bug fixes.
This is a big one.
NEW FEATURES:
1. By Request: Disk vendor is now generally going to be shown. Since this uses
empirical data to grab the vendor name, from the model string, it will not always
find anything. When it fails to find vendor data, no vendor: item will show.
Note that some MMC devices will probably not show vendor data, but that's due to
there being no data that reveals that.
2. Extended -sx volts to also show voltage from lm-sensors if present. Many
systems show no voltage data with lm-sensors, but now if any is found, it
will show, same as impi.
3. Moved to lsblk as primary source for partition/unmounted filesystem, uuid, and
label data.
Falls back to previous methods if lsblk does not return data. Some lsblk do not
show complete data unless super user as well.
4. Refactored code to be more logical and clear.
5. Added for OpenBSD -r: /etc/installurl file.
BUG FIXES:
1. CRITICAL: /sys/block/xxx/device/model is in some cases truncating the disk
model name to 16 characters. This is not an inxi bug, it's a bug with /sys itself.
To fix this, inxi now uses for GNU/Linux /dev/disk/by-id data which does not
ever do this truncation. It's also faster I believe to read that directory
once, filter the results, then use the data for vendor/model/serial.
this was also part of the disk vendor data feature.
2. Openbsd networking fix. Was not showing IF data, now it does.
3. Fixed bug with unmounted where sometimes md0 type partitions would show
even though they are in a raid array.
4. Fixed disk rev, now it searches for 3 different files in /sys to get that data.
5. Fixed bug with very old systems, with sudo 1.6 or older, for some reason that
error did not get redirected to /dev/null, so now only using sudo -n after explicit
version test, only if 1.7 or newer.
6. Fixed a few null results in fringe cases for graphics. Resolution now shows
NA for Hz if no hz data found. This was only present on a fringe user case
which is unlikely to ever impact normal X installations.
7. Fixed BSD L2 cache, was showing MiB instead of KiB, wrong math.
2018-05-07 03:43:34 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
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.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-E\fR, \fB\-\-bluetooth\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show bluetooth device(s), drivers. Show \fBReport:\fR with HCI ID, state,
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
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.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
If bluetooth shows as \fBstatus: down\fR, shows \fBbt\-service:\fR\fB state
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
and rfkill\fR software and hardware blocked states, and rfkill ID.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Note that \fBReport\-ID:\fR indicates that the HCI item was not able to be
|
|
|
|
|
linked to a specific device, similar to \fBIF\-ID:\fR in \fB\-n\fR.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
If your internal bluetooth device does not show, it's possible that
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
it has been disabled, if you try enabling it using for example:
|
|
|
|
|
|
|
|
|
|
\fBhciconfig hci0 up\fR
|
|
|
|
|
|
Bug fixes!! Fixes!!! Refactors!!! Edits!!!
Bugs:
1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and
partition scheme would never show, oops.
2. Tiny bug kept one specific smart value from ever showing, typo.
Fixes:
1. Accidentally followed Arch linux derived distro page, which claims KaOS as
arch derived, when of course it's not, it's its own distro, own toolchain, etc.
I kind of knew this but had forgotten, then I believed the Arch derived distro
page, oh well. Resulted in KaOS being listed with arch linux as system base
with -Sx. Arch should fix this, it's not like it's hard, just remove the distro
from the page.
2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends,
man, and help to hopefully make this clear. Debian will be dropping hddtemp,
which is not maintained, sometime in the coming years, sooner than later.
Note that users unfortunately have to manually enable drivetemp module unless
their distros enable it by default, but the man/recommands/help explain that.
3. Fixed smart indentation issues, that went along with code change 1, was
failing to indent one further level for failed/age values like it's supposed
to.
Enhancements:
1. Added /proc/device to debugger, that will help track block device main numbers
2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows
eternally, thanks linux-lite hardware database users!! and other inxi users,
whose outputs sometimes reveal a failure or two.
3. Added loaded kernel module tests to --recommends, this was mostly to let users
know that drivetemp is needed if you want non superuser fast drive temps, and
that this came along with kernels 5.6 or newer. Hopefully word will start drifting
out. Note that if inxi is using drivetemp values, drive temps will appear as
regular user with -Dx, and will be to 1 decimal place. hddtemp temps are
integers, and requires sudo to display the temps.
4. To handle issue #239 which I'd thought of trying off and on, but never did,
added option to -Dxxx to show SSD if a positive SSD ID was made to rotation:
So rotation will show either nothing, if no rotation or ssd data is detected,
the disk speed in rpm, or SSD if an SSD device. There may be corner cases where
this is wrong, but I don't have data for that, for example, if a disk is parked
and has zero rotation but is a HDD, not as SSD. I don't know what the data
looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is
installed, it should be right almost all the time, and with regular -Dxxx, it's
going to be right almost always, with a few corner cases. That slight
uncertainty is why I never implemented this before. Legacy drives also sometimes
did not report rotation speeds even when HDD, so those may create issues,
but inxi will only call it an SSD if it's an nvme, mmcblk device, both are
easy to ID as SSD, or if it meets certain conditions. It will not call a drive
an SSD if it was unable to meet those conditions.
INTERNAL CODE CHANGES:
1. Refactored the output logic for DiskData, that was messy, split it into a few
subs, and also refactored the way smartctl data was loaded and used, that's
much cleaner and easier to use now. Split the previous 1 big sub into:
totals_output(), drives_output(), and smart_output().
Also split out the smart field arrays into a separate sub, which loads
references to avoid creating new arrays and copying them all over when outputting
smart data. References are weird to work with directly but they are MUCH faster
to use, so I'm moving as much of the internal logic to use array raferences
instead of dereferenced arrays/hashes assigned to a new array, or hash.
2. Redid all the output modules and renamed them to be more consistent and
predictable, and redid the logic here and there to make the get() items be fairly
similar on all the data builder packages. Now as with the data subs, which
generally end in _data, now most of the output subs end with _output.
3. Roughly finished the process started in 3.2, got rid of redundant array loads,
changed:
@something = something_data();
push (@rows,@something);
to:
push (@rows,something_data());
which avoids creating an extra array, this also let me remove many arrays overall.
4. Missed a few hashes in machine data that were being passed directly, not as
references, to other subs, corrected that. I think I missed those because they
were %, so the search I did for @ in sub arg lists didn't catch the % hashes.
2021-02-09 01:07:34 +00:00
|
|
|
and it returns a blocked by RF\-Kill error, you can do one of these:
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
2021-02-09 01:15:46 +00:00
|
|
|
\fBconnmanctl enable bluetooth\fR
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBrfkill list bluetooth\fR
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
|
|
|
|
\fBrfkill unblock bluetooth\fR
|
|
|
|
|
|
New version, man. Continuing development of EDID and monitor features, bug
fixes, normal fixes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Failed to handle case for monitor positions of array type: 2-2, 3-1, 1-3,
4-4. I'm not sure what structure those are really arranged in, but might be
worth adding in the x+y pos values along with the row-col values.
2. For Monitors and graphics Device ports, if using non free nvidia driver and:
nvidia-drm.modeset=1 not set in grub kernel boot parameters, there will be no
/sys/class/drm data for the nvidia device, and thus no ports data, and no
monitor data.
3. A class of high count DP or DVI port IDs are changed by Xorg drivers to for
example: DP-6 > DP-2-3. This is very difficult to handle and will in general
probably fail unfortunately because that level of port ID abstraction is just
reazlly hard to deal with dynamically.
4. A to-do item: add bus ID children on --slots. This will probablby be in next
inxi.
--------------------------------------------------------------------------------
BUGS:
1. None outside of the various fixes.
--------------------------------------------------------------------------------
FIXES:
1. In sensors, failed to pull out BAT sensor data. In most cases, this would not
lead to any issues, but it could have.
2. This one just slipped my mind, I'd meant to do it, but in Montitor-x:, the
primary ID should have been the 'real' kernel ID, not the mapped: ID, which is
the X.org ID when different from the kernel ID. So mapped should be the Xorg
version when they are different from the kernel version.
3. In Graphics, monitors can show > 1 ratio, failed to set all to :, resulting
in: ratio: 3:2 or 16/10 modes:. Also fixed ParseEDID to output an array of
ratios, which can then be processed as wanted.
4. Monitor map fixes:
* Handle case in monitors where display ID: eDP and sys ID: eDP-1, this only
works if 1 monitor in array. There's a variety of this type of failure, when
X.org or its drivers decide to call the port ID XYZ with no number at all. All
those possible cases are now handled, like eDP > eDP-1, VGA > VGA-1, and so on.
* Added fallback, if no match, and if only 1 monitor, just map them to eachother
if other mappings failed. Prompted by things like: s: DP-6 > d: DP-2-3;
s: eDP-1 > d: DP-4, which are just impossible to create logic to map.
5. Removed 'ati' driver from xorg drivers list, it's simply a wrapper for r128,
mach64, or radeon (and maybe amdgpu), and shows as failed, unloaded, or loaded,
because of this. ati basically assigns the correct driver, that is, but is not
itself a driver. Thanks mrmazda for spotting this issue.
6. Typo on QDI => Quantum Data.
7. Added fallback for monitor model, now using vendor code plus product code
if nothing found for vendor nice name or model. This will show as 'model-id:'
instead of model: to help differentiate the two.
8. Added Monitor product_code to manufacturer if no model name is found.
9. get_pci_vendor was trimming at ' / ' if the product string also contained
' / '. Fix is to ignore 1 character 'words' in the logic.
10. In Slots, failed to remove_duplicates in the slot info field, leading to
redundant output strings. See Enhancement 3 and Code 4.
11. See Change 3, finally made -S section use full key: value pair, which makes
stuff more explicit, like:
System:
Host: yawn
Kernel: 5.16.0-11.1-liquorix-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 11.2.0
Desktop: Xfce
v: 4.16.0
tk: Gtk
v: 3.24.24
info: xfce4-panel
wm: xfwm
v: 4.16.1
vt: 7
dm:
1: LightDM
v: 1.26.0
2: SDDM
note: stopped
Distro: Debian GNU/Linux bookworm/sid
12. Fix for mageia and lsb distro data, force use of os-release for mageia if
detected. That overrides the forced use of lsb release for mandrake/mandriva,
because for some reason mageia has decided to carry ALL the legacy distro files:
'/etc/lsb-release',
'/etc/lsb-release.d',
'/etc/mageia-release',
'/etc/mandrake-release',
'/etc/mandrakelinux-release',
'/etc/mandriva-release',
'/etc/os-release',
'/etc/redhat-release',
'/etc/system-release'
which is really not what this stuff is intended for, if it's an actual derived
distro from a living base, then yes, include the base file, but all these have
the same distro id data for mageia, none for the derived distros.
Also, fixed an lsb release thing to avoid using codename if codename contains
release number as well. Since lsb_release is totally legacy at this point, who
cares if we might miss a specific codename here and there on legacy system.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added Color Characteristics to EDID parser, for some reason that had been
left out.
2. Added advanced EDID output option --edid, that allows for showing more
advanced EDID data than is appropriate for most users cases. Ihcludes errors,
color characteristics chroma: (chromacity), full modes, not just min/max.
3. In --slots, added bus-ID.
Also extended report quality, made more granular, got rid of single blob from
Type and Designation and now get more accurate and useful data.
4. In cases with > 1 DM, check to see if one or more are stopped or disabled, =
and add (stopped) if it was detected in running service as stopped.
--------------------------------------------------------------------------------
CHANGES:
1. Reversed monitor ID and mapped: ID values, that was a mistake, the mapped:
item was supposed to contain the X.org mapped name, and the primary ID was
supposed to be the actual real ID the kernel uses. Not a huge deal either way,
but there it is.
2. Include disabled but connected Monitors. This works around nvidia bug showing
monitors disabled when they are enabled, but also allows for showing connected
monitors, though without as much data.
3. Made the last holdout -S > -Sa use strict full key: value pair output, like
Desktop: XFCE v: 4.14.12 and so on.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added help/man for --edid info.
--------------------------------------------------------------------------------
CODE:
1. In ParseEDID: made new key: edid_error, which contains an array ref of 1 or
more edid errors. The previous version did a poor job and returned only the
first error found, so there could have been > 1 error, and you'd never know it.
This changes check_parsed_edid to _check_parsed_edid(). and adds a utility tool
_edid_error, which grabs the message from main::message, giving better output
integration.
This also allows for future error handling expansion quite easily.
2. In map_monitor_ids() fixed matching pattern, made more robust and explicit,
to catch things like s: eDP-1 d: eDP or eDP-1-1, both have been seen. Also added
fallback for single monitor, just map them to eachother if mapping failed.
3. get_pci_vendor() added test for using anything that is 1 character length,
to not break on 1 character length string matches.
4. Fully refactored --slots, that was originally written purely as a proof of
concept in terms of adding a new feature during the original inxi 2.9 rewrite,
and was never actually touched after that.
2022-03-24 18:45:05 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-edid\fR
|
|
|
|
|
.br
|
|
|
|
|
Triggers full \fBEDID\fR data in Graphics, activates \fB\-G\fR and \fB\-a\fR.
|
|
|
|
|
|
|
|
|
|
\- Adds monitor chromacity (\fBchroma: red:..green:...blue:...white:\fR).
|
|
|
|
|
|
|
|
|
|
\- Shows all available monitor modes if > 2 present, in comma separated list.
|
|
|
|
|
|
|
|
|
|
\- Shows \fBEDID\fR errors and warnings if any present.
|
|
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-filter\fR, \fB\-z\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fBFILTER OPTIONS\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-f \fR, \fB\-\-flags\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show all CPU flags used, not just the short list. Not shown with \fB\-F\fR
|
|
|
|
|
in order to avoid spamming. ARM CPUs: show \fBfeatures\fR items.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-F \fR, \fB\-\-full\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show Full output for inxi. Includes all Upper Case line letters (except
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fB\-J\fR and \fB\-W\fR) plus \fB\-\-swap\fR, \fB\-s\fR and \fB\-n\fR. Does not
|
|
|
|
|
show extra verbose options such as \fB\-d \-f \-i -J \-l \-m \-o \-p \-r \-t \-u
|
|
|
|
|
\-x\fR unless you use those arguments in the command, e.g.:
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBinxi \-Frmxx\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-gpu\fR
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
Deprecated. See \fB\-G \-a\fR.
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-G \fR, \fB\-\-graphics\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show Graphic device(s) information, including details of device and display
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
drivers (\fBX:\fR \fBloaded:\fR, and, if applicable: \fBunloaded:\fR,
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\fBfailed:\fR, \fBdri:\fR (if X and different from loaded X drivers) drivers,
|
|
|
|
|
and active \fBgpu:\fR drivers), display protocol (if available), display server
|
|
|
|
|
(and/or Wayland compositor), vendor and version number, e.g.:
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fBDisplay: x11 server: Xorg v: 1.15.1\fR
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
or:
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
|
|
|
|
|
\fBDisplay: wayland server: X.org v: 1.20.1 with: Xwayland v: 20.1\fR
|
2017-06-25 01:28:24 +00:00
|
|
|
|
New version, new man. Fine tunings.
New features:
1. for a very few systems that have wmctrl installed, will shows -xxx wm if present
Enhancements:
1. made xorg display server and protocols show more consistently with other layout:
Display: x11 server: X.org 1.9.12 drivers: loaded: ...
if no display protocol found:
Display: server: X.org 1.9.12 drivers: loaded: ...
This brings the -G in line with the other lines, of not putting different data types
inside of parentheses as much as possible. -I still has two of these, but so far it's
not clear how to otherwise show SSH or su/sudo/login in their respective spaces.
Debugger data collector also has something I should have added ages ago, gz filename
now includes the basic 2 digit inxi version number, like 3.0 at end, so I can readily
determine the debugger inxi version, and thus avoid having to root through lots of
versions to find new stuff.
These are all largely cosmetic improvements, or debugger adjustments, except for -Sxxx
now offering wm: if present.
Also changed Desktop: name... (toolkit data) to: Desktop: name... tk: toolkit data
to be more consistent, while not adding great length to the output.
These two changes should also help export to json/xml since that puts unique key/values
back into key value pairs, not merging two together.
2018-04-12 20:23:46 +00:00
|
|
|
If protocol is not detected, shows:
|
|
|
|
|
|
|
|
|
|
\fBDisplay: server: Xorg 1.15.1\fR
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
Adds \fBwith: Xwayland v:...\fR if xwayland server is installed, regardless of
|
|
|
|
|
protocol.
|
|
|
|
|
|
This release fixes another very long standing bug, which I was not sure was an
inxi or a Konversation bug, which made tracking it down very difficult. Special
thanks to argonel of Konversation for helping solve this problem, or at least,
for directing my attention towards the likely cause area, and away from wrong
ideas. The bug was that inxi simply did not run in Konversation, it would exit
with error when run with /cmd or /inxi via symbolic links.
This may not seem like a huge deal to many of you, but the actual history of
inxi was directly linked to user support in mainly Konversation, so this feature
not working I have alwyas found extremely annoying, but I could never figure out
why it wasn't workiing, and didn't really know where to start until Argonel
helped narrow it down to a specific Konversation function in inxi. At which
point tracking down the real bug was fairly easy. Since testing in IRC is always
a key test point for inxi features and releases, not working in my main GUI IRC
client forced me to use CLI clients like irssi, via /exec -o inxi.
There was a secondary cause of failure, which was missing a key qdbus package,
which made figuring this one out a two step process.
So inxi is once again working in all areas, with no known significant failure
areas beyond known issues that have no current solution, or which I don't feel
like doing.
But possibly more important, a goal I have had for a while now of doing long
needed code refactors, bug fixes, without huge new code blocks or features
adding new future fixes and bugs, has been slowly happening.
This was quite important, because inxi's codebase and logic is so complex and
large now that at some point, it required rest and cleanup and corrections,
without continuously adding new code and logic, which would then trigger new
fixes and bugs. In other words, the code is taking a long needed, and well
deserved, breather, to recover after huge increases in the overall LOC and
feature sets.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. No known way to detect that the system might be Wayland for the Graphics:..
API: fixes, unless Xwayland is installed if the wayland protocol detections
failed, which they often do in console. Not practical to look for all compositor
variants on system to determine if it could be Wayland if not X or Xvesa, so
that one will just be what it is, which is fine, definitely better than it was
before. Note this is only an issue if in Console, no Display. Note that if inxi
is run as root, Wayland data also usually fails, even in Display.
--------------------------------------------------------------------------------
BUGS:
1. Another corner case monitor position issue, applied fallback primary monitor
rule when a primary monitor had already been located. This is corrected via a
graphics global $b_primary which once set will disable this fallback feature.
Objectively, the fallback feature should just be removed. The test is if that
monitor is not primary, and if position is 0x0, then assume primary, without
verifying no primary had been located yet.
2. A super old bug, in current konversation, was failing to trip the konvi
detections, which then resulted in not stripping off the first two args in
@ARGV, which then resulted in bad args being passed to inxi on konvi start,
which then resulted in silent failing. Many thanks to argonel of #konversation
for the patience to help me figure out what was going on with this bug. He's
been a Konversation developer probably longer than I've been doing inxi.
Cause was very tricky and subtle, the ps aux path for konvi had changed
slightly, not the path, but the pattern, it used to be:
konversation -session [sessin id]
but it's changed to:
konversation -qwindowtitle Konversation
or just plain:
konversation as line ending.
This led to failure to find konvi running, which then made the konvi ids fail.
Also, this would not work if the qdbus-qt5 package was not installed, or other
distros might have that packaged differently. Because of these dual causes, I
was simply unable to figure out what was going on for many years. I suspect this
stopped working with KDE 5/QT 5, but I'm not sure.
3. Used wrong key names for some ZFS tests and fallbacks, those could have led
to failures though very difficult to test and verify this. Also see fix 5, which
of course also looks like a bug, acts like one, but was actually due to a new
use of /dev/disk/by-partuuid for ZFS components in Ubuntu which inxi had not
seen before.
--------------------------------------------------------------------------------
FIXES:
1. Alternate ps IDs for appimage detection (try appimagelauncher), alternate
paths for possible appimage storage locations (also try ~/.appimage/*). File
names might be *.appimage or *.AppImage, probably other variants too.
2. Going along with Change 1, made tests more granular for missing graphics API
type data. Also updated messages to be more correct and clear, in and out of
display. This corrects an issue I'd seen but never resolved, which was on
headless systems showing this message:
Message: GL data unavailable in console. Try -G --display
Now the tests are far more granular, and only show that if glxinfo is installed,
and also shows specific messages if glxinfo not installed, but X/Xorg present,
or, for Wayland, if Xwayland present. These all get their own specific messages
now, and generally will also show which API is being used, or API: N/A if
nothing is detected, as in the case of a headless system with no X, Wayland,
etc.
3. Github issue #275 on of all things Microsoft WSL environment, has a small
glitch with undefined display hz, but otherwise inxi seems to work in that
environment, albeit missing many data types!
4. Made tests for konversation more robust, including test for
$ENV{'PYTHONPATH'} containing konversation in path, which I believe will work
for all new Konversations (KDE 5 and newer), and be much faster. The previous
tests are now more robust and less prone to failure, and only activate when
PYTHONPATH is not present with konversation string present as well.
5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs,
which can lead to wrong usable disk total size report, along with failure
to show components. Thanks delanym, issue #276 for reporting this problem, which
also exposed some harder to trigger bugs in ZFS (Bug 3).
6. Exposed by issue #276, case where line was wrapping value when value was too
short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words
trigger to enable wrapping of value, but noticed that if length of line was
exactly max-width, not > or <, it might vanish.
7. Case where no X or GPU drivers found, but dri driver detected, was not
showing, now does.
8. OpenRC is the init system in some cases, that is: readlink /sbin/init >
/sbin/openrc-init, where /proc/1/comm == init. Was showing only as OpenRC rc
type, which wasn't actually correct.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New nvidia gpu product ids for Turing, Ampere, Lovelace, Hopper. New Intel
GPU ids.
2. Added Zinc to systembase/distro, needs slightly special handling to get both
names right. Also added Tuxedo, which could use existing methods.
3. Added dpkg tool nala, which is sort of a CLI front end for apt, zinc uses it,
but it's also in Debian main package pool. Also deb-get, which is another zinc
thing for package management.
4. Full support for dinit: version, dinitctl w/status in ServiceData
4. Added initial support for init systems: 31init (31 line C program, no
--version), Hummingbird (unknown if -v/--version).
5. A few new CPU arch ids (new Intels).
--------------------------------------------------------------------------------
CHANGES:
1. Going somewhat along with the change in Audio to call ALSA a Sound API
instead of a sound server, changed key name OpenGL: to API: OpenGL in Graphics.
Also for EGL wayland, calling that the api too.
https://en.wikipedia.org/wiki/OpenGL
This conforms more closely to how these things are defined. Note that once
again, a value had been used as a key name, which almost always indicates a
failure to understand something about the core tech.
2. Changed wrapping of values from 3 words or more to 3 or more words AND length
> 24 characters. Saw example of:
.... used: 28.45 GiB
(4.5%)
which isn't desirable.
3. Changed minimum wrap to 60 columns, the new wrapper features are working so
well that if users want output that short, it will usually work fine, except of
course for very long word strings like a kernel name or parameter.
Note that this does not truncate long 'words' that might be wrapped, or going
along with Change 2, long 'sentences' of 2 words, those will always appear on
the same line regardless. For 'sentences' of 3 or more words, however, it goes
word by word, so it could well wrap after the first word, and so on. Obviously,
a 24 or fewer character value will never be wrapped, which was the intended
correction of change 2.
4. Going with Fix 8, OpenRc is an init system when it owns /proc/1/comm, had not
realized that /proc/1/comm == init can map to dinit, openrc as init. Now will
only show OpenRc as rc: type if not init as well.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updates in man for Change 1.
2. Added to docs/inxi-graphics.txt good quote re EGL/GBM, as well as VBE/GOP for
vesa. Trying to find docs where they actually say clearly it's an API is
remarkably difficult.
3. Man page, added note about Konversation requiring qdbus-qt5 (Debian+),
qt5-qttool (RHEL+/SUSE+), qt-tools (Arch+) for inxi to work inside it. Also
updated smxi.org/docs/inxi-usage.txt to note requirements for Konversation use
and setup.
4. Man, help, changed min width for -y/--width from 80 to 60.
5. docs/inxi-values.txt updated for --cygwin, --wsl fake OS type switches. Not
technically the OS, more the environment, but close enough.
6. docs/inxi-init.txt updated for new init types.
--------------------------------------------------------------------------------
CODE:
1. Refactored tools/gpu_ids.pl to correct and enhance some features.
2. Renamed functions and sections to better reflect that the display interface
is an API, this makes stuff less odd internally, and makes the function/variable
names correspond better to what the stuff really is.
3. Commented out kde konversation data source config collector, that logic looks
like it never worked, and couldn't work, since it never actually located
inxi.conf files, just paths to the data directories.
4. Expanded release.pl to handle acxi docs as well, makes it all consistent and
a lot easier to do long term.
5. Fake --wsl WSL switch, not really used, but in case.
6. Changed $b_cygwin to $windows{'cygwin'} and added $windows{'wsl'}.
7. Added -WSL to debugger string generator once WSL type is detected.
8. Refactored init, runlevel functions get_init_data() (now InitData::get()),
get_runlevel_data() (now InitData::get_runlevel()), get_runlevel_default() (now
InitData::get_runlevel_default()) into one package/class: InitData. This should
have been done a long time ago, to follow the general rule "if > 1 functions for
a tool refactor it into a class/package" for when to create a package/class
internally.
9. Completed gpu_ids.pl, now outputs the full hash set per item, so entire
blocks can be copied/pasted over. Something of a pain to get comments included,
which aren't strictly necessary in pinxi itself, but they do help read the
hashes for gpu data.
2022-10-31 22:47:31 +00:00
|
|
|
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).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
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.
|
|
|
|
|
|
New version, man. Continuing development of EDID and monitor features, bug
fixes, normal fixes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Failed to handle case for monitor positions of array type: 2-2, 3-1, 1-3,
4-4. I'm not sure what structure those are really arranged in, but might be
worth adding in the x+y pos values along with the row-col values.
2. For Monitors and graphics Device ports, if using non free nvidia driver and:
nvidia-drm.modeset=1 not set in grub kernel boot parameters, there will be no
/sys/class/drm data for the nvidia device, and thus no ports data, and no
monitor data.
3. A class of high count DP or DVI port IDs are changed by Xorg drivers to for
example: DP-6 > DP-2-3. This is very difficult to handle and will in general
probably fail unfortunately because that level of port ID abstraction is just
reazlly hard to deal with dynamically.
4. A to-do item: add bus ID children on --slots. This will probablby be in next
inxi.
--------------------------------------------------------------------------------
BUGS:
1. None outside of the various fixes.
--------------------------------------------------------------------------------
FIXES:
1. In sensors, failed to pull out BAT sensor data. In most cases, this would not
lead to any issues, but it could have.
2. This one just slipped my mind, I'd meant to do it, but in Montitor-x:, the
primary ID should have been the 'real' kernel ID, not the mapped: ID, which is
the X.org ID when different from the kernel ID. So mapped should be the Xorg
version when they are different from the kernel version.
3. In Graphics, monitors can show > 1 ratio, failed to set all to :, resulting
in: ratio: 3:2 or 16/10 modes:. Also fixed ParseEDID to output an array of
ratios, which can then be processed as wanted.
4. Monitor map fixes:
* Handle case in monitors where display ID: eDP and sys ID: eDP-1, this only
works if 1 monitor in array. There's a variety of this type of failure, when
X.org or its drivers decide to call the port ID XYZ with no number at all. All
those possible cases are now handled, like eDP > eDP-1, VGA > VGA-1, and so on.
* Added fallback, if no match, and if only 1 monitor, just map them to eachother
if other mappings failed. Prompted by things like: s: DP-6 > d: DP-2-3;
s: eDP-1 > d: DP-4, which are just impossible to create logic to map.
5. Removed 'ati' driver from xorg drivers list, it's simply a wrapper for r128,
mach64, or radeon (and maybe amdgpu), and shows as failed, unloaded, or loaded,
because of this. ati basically assigns the correct driver, that is, but is not
itself a driver. Thanks mrmazda for spotting this issue.
6. Typo on QDI => Quantum Data.
7. Added fallback for monitor model, now using vendor code plus product code
if nothing found for vendor nice name or model. This will show as 'model-id:'
instead of model: to help differentiate the two.
8. Added Monitor product_code to manufacturer if no model name is found.
9. get_pci_vendor was trimming at ' / ' if the product string also contained
' / '. Fix is to ignore 1 character 'words' in the logic.
10. In Slots, failed to remove_duplicates in the slot info field, leading to
redundant output strings. See Enhancement 3 and Code 4.
11. See Change 3, finally made -S section use full key: value pair, which makes
stuff more explicit, like:
System:
Host: yawn
Kernel: 5.16.0-11.1-liquorix-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 11.2.0
Desktop: Xfce
v: 4.16.0
tk: Gtk
v: 3.24.24
info: xfce4-panel
wm: xfwm
v: 4.16.1
vt: 7
dm:
1: LightDM
v: 1.26.0
2: SDDM
note: stopped
Distro: Debian GNU/Linux bookworm/sid
12. Fix for mageia and lsb distro data, force use of os-release for mageia if
detected. That overrides the forced use of lsb release for mandrake/mandriva,
because for some reason mageia has decided to carry ALL the legacy distro files:
'/etc/lsb-release',
'/etc/lsb-release.d',
'/etc/mageia-release',
'/etc/mandrake-release',
'/etc/mandrakelinux-release',
'/etc/mandriva-release',
'/etc/os-release',
'/etc/redhat-release',
'/etc/system-release'
which is really not what this stuff is intended for, if it's an actual derived
distro from a living base, then yes, include the base file, but all these have
the same distro id data for mageia, none for the derived distros.
Also, fixed an lsb release thing to avoid using codename if codename contains
release number as well. Since lsb_release is totally legacy at this point, who
cares if we might miss a specific codename here and there on legacy system.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added Color Characteristics to EDID parser, for some reason that had been
left out.
2. Added advanced EDID output option --edid, that allows for showing more
advanced EDID data than is appropriate for most users cases. Ihcludes errors,
color characteristics chroma: (chromacity), full modes, not just min/max.
3. In --slots, added bus-ID.
Also extended report quality, made more granular, got rid of single blob from
Type and Designation and now get more accurate and useful data.
4. In cases with > 1 DM, check to see if one or more are stopped or disabled, =
and add (stopped) if it was detected in running service as stopped.
--------------------------------------------------------------------------------
CHANGES:
1. Reversed monitor ID and mapped: ID values, that was a mistake, the mapped:
item was supposed to contain the X.org mapped name, and the primary ID was
supposed to be the actual real ID the kernel uses. Not a huge deal either way,
but there it is.
2. Include disabled but connected Monitors. This works around nvidia bug showing
monitors disabled when they are enabled, but also allows for showing connected
monitors, though without as much data.
3. Made the last holdout -S > -Sa use strict full key: value pair output, like
Desktop: XFCE v: 4.14.12 and so on.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added help/man for --edid info.
--------------------------------------------------------------------------------
CODE:
1. In ParseEDID: made new key: edid_error, which contains an array ref of 1 or
more edid errors. The previous version did a poor job and returned only the
first error found, so there could have been > 1 error, and you'd never know it.
This changes check_parsed_edid to _check_parsed_edid(). and adds a utility tool
_edid_error, which grabs the message from main::message, giving better output
integration.
This also allows for future error handling expansion quite easily.
2. In map_monitor_ids() fixed matching pattern, made more robust and explicit,
to catch things like s: eDP-1 d: eDP or eDP-1-1, both have been seen. Also added
fallback for single monitor, just map them to eachother if mapping failed.
3. get_pci_vendor() added test for using anything that is 1 character length,
to not break on 1 character length string matches.
4. Fully refactored --slots, that was originally written purely as a proof of
concept in terms of adding a new feature during the original inxi 2.9 rewrite,
and was never actually touched after that.
2022-03-24 18:45:05 +00:00
|
|
|
\fB\-Gxx\fR shows monitor data as well, if detected. \fB\-\-edid\fR shows
|
|
|
|
|
advanced monitor data (full modes, chroma, etc.).
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-h \fR, \fB\-\-help\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
The help menu. Features dynamic sizing to fit into terminal window. Set script
|
|
|
|
|
global \fBCOLS_MAX_CONSOLE\fR if you want a different default value, or use
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fB\-y [width]\fR to temporarily override the defaults or actual window width.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-i \fR, \fB\-\-ip\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Show WAN IP address and local interfaces (latter requires \fBifconfig\fR or
|
|
|
|
|
\fBip\fR network tool), as well as network output from \fB\-n\fR. Not shown with
|
|
|
|
|
\fB\-F\fR for user security reasons. You shouldn't paste your local/WAN IP.
|
|
|
|
|
Shows both IPv4 and IPv6 link IP addresses.
|
New version, new tarball, new man page. This corrects several oversights of the 2.3.10 IPv6 update.
Now there is an -x option for -i that will show the additioanl IPv6 address data for scope global,
temporary, and site. Also a fallback for unhandled scope: unknown. If the tool 'ip' is used, it will
filter out the deprecated temp site/global addresses, ifconfig tool does not appear to offer this
option.
Also changed is that now ipv6 address always shows, it's not an -x option. Probably about time to
start rolling out ip v6 data to users now that ip v6 is starting, slowly, to be used more.
Another small change, the link address for ipv6 is changed from ip-v6: to ip-v6-link so that it's
more clear which IP v6 address it is.
The last commit had a significant logic error in it that did not distinguish between the link address,
which is what should have only shown, and the remaining possible addresses.
I've tried to get a basic bsd support, but it's difficult to know the variants of ifconfig output syntax
2017-05-31 22:33:16 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-I \fR, \fB\-\-info\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
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
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
for extra information (init type/version, runlevel/target, packages).
|
New version, new man. Changes, bug fixes, enhancements! Don't delay!
Bugs:
1. A real bug, the detection for true path of /dev/root had a mistake in it and
would only have worked in half the cases. This was an easy fix, but a significant
but since it also would lead to the actual root / partition showing in Unmounted.
2. Related to the item Fixes-2, if two USB networking devices were attached,
the second one's bus and chip ID would go on the wrong line of data if -n or -i
option were used. Since that would be the line belonging to the one above,
that obviously was weird and wrong.
3. NEW: latest kernel can show hwmon data in sensors, for example from wifi chip.
This broke CPU temp detection and showed way too high cpu temp, so this fix is
fairly important since new kernels may have this new sensors hwmon syntax.
4. Sensors: IPMI alternate syntax found, also case with no data in expected columns,
just N/A, so now the ipmi sensor logic skips all lines with non numeric values in
the values column. This is what it should have done all along, it was trusting
that values would always exist for the field names it looks for.
Fixes:
1. ARM networking fix. ARM devices like rasberry pi that use usb bus for networking
showed the no data message even though usb networking was right below it. This is
corrected, and now that only shows if both main and usb networking failed for ARM.
2. Big repo fix: while testing distro and Trinity live cds, I discovered that apt is
sometimes used with rpms, which made PCLinuxOS and ALT-Linux Repos item show the
apt files but no data since the pattern was looking for start with deb. Added rpm
to pattern, so all distros that use apt running rpms should now 'just work'.
3. Fixed more distro id things, PCLinuxOS should now show its full distro string.
4. Debugger: Filtered out more blocks of /proc, that data is bloated and messy, found
another case where it collected a vast amount of junk system data from zfs in that
case, just blocked the entire range. I had no idea /proc had so much junk data in it!
5. As noted above, IPMI, yet another alternate syntax for field names. My hope that
IPMI software and sensors will be more logical and consistent than lm-sensors output
is proving to be merely wishful thinking, I think now out of 3 datasets I've gotten,
I've seen 3 variants for syntax, not to mention the ipmi-tool vs ipmi-sensors
differences. So IPMI will be like all sensors stuff, a work in progress, to
be updated with every newly discovered alternate syntax and data set.
Enhancements:
1. Disk vendors, added some, improved pattern detections for others. This feature
is getting better all the time. Thanks linuxlite hw db, easy to scan for missing
vendors in their inxi data.
2. Added more wm, budgie-wm, mwm, variants of kwin and Trinity's Twin, several others,
more refactoring of core wm/desktop code.
3. Added gpu ram and reworked memory logic for rasberry pi, which is the only SBC
I am aware of that uses that tool. Now reports the actual total, and also gpu: for
ram data, so you can tell that the gpu is using part of the total. Again, this comes
from issue #153. Also added that info to man page for -I part.
4. Added more ARM and PCI cleaners for neater and more concise ARM/PCI output.
5. Added Trinity support to Desktop section, this had at least two different detection
methods, but since the first just shows KDE original data, only the second one proved
to be Trinity specific. Happily, the full data is available, toolkit, desktop version,
and wm (Twin).
6. New -G,-A,-R -xxx feature: vendor:. Note that vendor data is very bloated and
messy so it's trimmed down substantially, using a series of filters and rules, and
thus it can contain the following: the actual vendor, like Dell, nothing, the
motherboard vendor/product for board based PCI items, or a complete vendor/product
string if it's unique. I couldn't think of a clean field name that meant:
vendor OR vendor + basic product info OR motherboard + board version OR full
product name, including vendor, so in the end, I just used vendor: but it's not
quite the right term, but nothing else seemed to work better. Testers responded
very enthusiastically about this feature so I guess the vendor: name is ok.
Changes:
1. Biggest change: Drives: HDD: total: the HDD: is now changed to: Local Storage:
This was part of issue #153 and is a good suggestion because HDD generally was used
to refer to hard disks, spinning, but with nvme, m.2, ssd, etc, that term is a bit
dated. 'Local' is because inxi does not include detected remote storage in the totals.
2. The recent --wm option which forced ps as data source for window manager detection
has been reversed, now --wm forces wmctrl and ps aux is preferred. Still falls back
to wm ctrl in case the ps test is null, this is better because I have to add the wm
data manually for each one, whereas wmctrl has an unknown set and probably variable
set of wm. Note that I reversed this because I saw several cases where wmctrl was
wrong, and reported a generic source wm instead of the real one. Since most uses are
not going to even be aware of the wm: feature as enhanced with --wm switch, this
should have no impact on users in general. Since the detected wm name needs to be
know to get assigned to wm: and wm version data, I think it will work better to
have the known variants match with the wm data values, then just fallback to
unknown ones that can get fille in over time as we find wm that people actually
use and that you can get version info on and detect.
Removed:
1. Got rid of tests for GTK compiled with version for many desktops, that test
was always wrong because it did not have any necessary relation to the actual
gtk version the desktop was built out of, and it also almost always returned no
data. Since this is an expensive and slow test, and is always going to be wrong
or empty anyway, I've removed it. My tests showed it taking about 300ms or so
to generate no data, heh.
That's the tk: feature in -S. Note I also found that gnome-shell takes
an absurdly long time to give --version info, the slowest of all such things, 300ms
again, just to show version? Someone should fix that, there's no possible reason
why it should take 300 milliseconds to give a simple version string. Note that
this returns tk: to only returning real data, which in this case means only xfce,
kde, and trinity, which are the only desktops that actually report their toolkit
data. I'll probably remove that code in the future unless I can think of some real
use for gtk version elsewhere, but it's just junk data which doesn't even work.
In the future, I will not try to emulate or guess at desktop toolkits, either they
show the data in a direct form like XFCE or Trinity or KDE do, or I won't waste
resources and execution time making bad guesses using inefficient code and logic.
QT desktops like LXQt I'm leaving in because I believe those will tend to track
more closely the QT version on the system, and the tests for QT version aren't
huge ugly hacks the way they are for GTK, so they aren't as slow or intrusive, but
those may also get removed since they almost never work either. But they are also
slowing down the -Sx process so maybe they should be removed as well, I'll think
about it. Since they only are used on LXQt and razer-qt, it probably isn't a big
deal overall.
2018-07-12 21:35:09 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
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.
|
|
|
|
|
|
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 21:18:45 +00:00
|
|
|
See \fB\-m\fR for explanation of \fBMemory:\fR fields and values..
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-j\fR, \fB\-\-swap\fR
|
|
|
|
|
Shows all active swap types (partition, file, zram). When this option is used,
|
|
|
|
|
swap partition(s) will not show on the \fB\-P\fR line to avoid redundancy.
|
|
|
|
|
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
To show partition labels or UUIDs (when available and relevant), use with
|
|
|
|
|
\fB\-l\fR or\fB \-u\fR.
|
|
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-J \fR, \fB\-\-usb\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Show USB data for attached Hubs and Devices. Hubs also show number of ports. Be
|
|
|
|
|
aware that a port is not always external, some may be internal, and either used
|
|
|
|
|
or unused (for example, a motherboard USB header connector that is not used).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
Hubs and Devices are listed in order of BusID.
|
|
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
BusID is generally in this format: BusID\-port[.port][.port]:DeviceID
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Device ID is a number created by the kernel, and has no necessary ordering or
|
|
|
|
|
sequence connection, but can be used to match this output to lsusb values, which
|
|
|
|
|
generally shows BusID / DeviceID (except for tree view, which shows ports).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2020-04-23 03:04:46 +00:00
|
|
|
Examples: \fBDevice\-3: 4\-3.2.1:2\fR or \fBHub: 4\-0:1\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
The \fBrev: 2.0\fR item refers to the USB revision number, like \fB1.0\fR or
|
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 18:59:56 +00:00
|
|
|
\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.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-l \fR, \fB\-\-label\fR
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
Show partition labels. Use with \fB\-j\fR, \fB\-o\fR, \fB\-p\fR, and \fB\-P\fR
|
|
|
|
|
to show partition labels. Does nothing without one of those options.
|
|
|
|
|
|
|
|
|
|
Sample: \fB\-ojpl\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-L\fR, \fB\-\-logical\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Show Logical volume information, for LVM, LUKS, bcache, etc. Shows size, free
|
|
|
|
|
space (for LVM VG). For LVM, shows \fBDevice\-[xx]: VG:\fR (Volume Group)
|
|
|
|
|
size/free, \fBLV\-[xx]\fR (Logical Volume). LV shows type, size, and components.
|
|
|
|
|
Note that components are made up of either containers (aka, logical devices), or
|
|
|
|
|
physical devices. The full report requires doas/sudo/root.
|
|
|
|
|
|
|
|
|
|
Logical block devices can be thought of as devices that are made up out of
|
|
|
|
|
either other logical devices, or physical devices. inxi does its best to show
|
|
|
|
|
what each logical device is made out of. RAID devices form a subset of all
|
|
|
|
|
possible Logical devices, but have their own section, \fB\-R\fR.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
If \fB\-R\fR is used with \fB\-Lxx\fR, \fB\-Lxx\fR will not show RAID
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
information for LVM RAID devices since it's redundant. If \fB\-R\fR is not used,
|
|
|
|
|
a simple RAID line will appear for LVM RAID in \fB\-Lxx\fR.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fB\-Lxx\fR also shows all components and devices. Note that since components
|
|
|
|
|
can go in many levels, each level per primary component is indicated by either
|
|
|
|
|
another 'c', or ends with a 'p' device, the physical device. The number of c's
|
|
|
|
|
or p's indicates the depth, so you can see which component belongs to which.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fB\-L\fR shows only the top level components/devices (like \fB\-R\fR).
|
|
|
|
|
\fB\-La\fR shows component/device size, maj:min ID, mapped name (if applicable),
|
|
|
|
|
and puts each component/device on its own line.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
Sample:
|
|
|
|
|
|
|
|
|
|
.nf
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fB Device\-10: mybackup type: LUKS dm: dm\-28 size: 6.36 GiB Components:
|
|
|
|
|
c\-1: md1 cc\-1: dm\-26 ppp\-1: sdj2 cc\-2: dm\-27 ppp\-1: sdk2\fR
|
|
|
|
|
\fBLV\-5: lvm_raid1 type: raid1 dm: dm\-16 size: 4.88 GiB
|
|
|
|
|
RAID: stripes: 2 sync: idle copied: 100% mismatches: 0
|
|
|
|
|
Components: c\-1: dm\-10 pp\-1: sdd1 c\-2: dm\-11 pp\-1: sdd1 c\-3: dm\-13
|
|
|
|
|
pp\-1: sde1 c\-4: dm\-15 pp\-1: sde1\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.fi
|
|
|
|
|
|
|
|
|
|
It is easier to follow the flow of components and devices using \fB\-y1\fR. In
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
this example, there is one primary component (c\-1), md1, which is made up of
|
|
|
|
|
two components (cc\-1,2), dm\-26 and dm\-27. These are respectively made from
|
|
|
|
|
physical devices (p\-1) sdj2 and sdk2.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
.nf
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
\fBDevice\-10: mybackup
|
|
|
|
|
maj\-min: 254:28
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
type: LUKS
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
dm: dm\-28
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
size: 6.36 GiB
|
|
|
|
|
Components:
|
|
|
|
|
c\-1: md1
|
|
|
|
|
maj\-min: 9:1
|
|
|
|
|
size: 6.37 GiB
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
cc\-1: dm\-26
|
|
|
|
|
maj\-min: 254:26
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
mapped: vg5\-level1a
|
|
|
|
|
size: 12.28 GiB
|
|
|
|
|
ppp\-1: sdj2
|
|
|
|
|
maj\-min: 8:146
|
|
|
|
|
size: 12.79 GiB
|
|
|
|
|
cc\-2: dm\-27
|
|
|
|
|
maj\-min: 254:27
|
|
|
|
|
mapped: vg5\-level1b
|
|
|
|
|
size: 6.38 GiB
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
ppp\-1: sdk2
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
maj\-min: 8:162
|
|
|
|
|
size: 12.79 GiB\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
Bug Fixes!!! Continuing internal refactor!!
This bug report came in right after 3.2.00 went out live, but I would never have
found it myself in testing so better found than not found!
Bugs:
1. A bug was introduced to dmidecode data handlers in 3.2.00 resulted in the
dmidecode data array basically eating itself up until errors appear. Quite difficult
to trigger, but babydr from Slackware forums figured it out, using -F --dmidecode
to force dmidecode use for all features that support it triggered thee bug always.
This was a result of the refactor, previously inxi had worked on copies of referenced
arrays, but in this case, it was working on the original array of arrays, subtle,
but obvious. This method was only used on dmidecode arrays.
2. A second bug was exposed almost by accident, for -M --dmidecode data, there was
a missing field and also a missing is set test on that field that led to an error
of using undefined value in string comparison. This was strictly speaking 2 bugs,
both very old, from 2.9 first rewrite, one failing to set/get the value, and the
other failing to test if the value was set before using it.
Fixes:
1. There were a few glitches in help menu and man page related to -L option, those
are corrected.
INTERNAL CODE CHANGES:
1. removed bug inducing splice use in some cases, and added parens to splice to make
it fit the new way of with perl builtins, when taking 2 or more arguments, use parens.
2. Found many more instances to add -> dereferencing operator. I have to say, not
doing that consistently made the code much harder to read, and created situations
where it's somewhat ambiguous what item belongs to what, with everything consistently
-> operator run, the code is more clear and obvious, and some of the hacks I'd added
because of the lack of clarity were also removed.
3. Removed explicit setting of hash references with null value, that was done out
of failure to use -> operators which clearly indicate to Perl and coder what is
happening, so those crutches were removed. Also got rid of unnecessary array
priming like: my @array = (); Some of these habits came from other languages,
but in Perl, declaring my @array means it's an array that is null, and you don't
need to do a further (). @array = () is obviously fine for resetting arrays in
loops or whatever, but not in the initial declaration.
2020-12-17 22:51:11 +00:00
|
|
|
Other types of logical block handling like LUKS, bcache show as:
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Bug Fixes!!! Continuing internal refactor!!
This bug report came in right after 3.2.00 went out live, but I would never have
found it myself in testing so better found than not found!
Bugs:
1. A bug was introduced to dmidecode data handlers in 3.2.00 resulted in the
dmidecode data array basically eating itself up until errors appear. Quite difficult
to trigger, but babydr from Slackware forums figured it out, using -F --dmidecode
to force dmidecode use for all features that support it triggered thee bug always.
This was a result of the refactor, previously inxi had worked on copies of referenced
arrays, but in this case, it was working on the original array of arrays, subtle,
but obvious. This method was only used on dmidecode arrays.
2. A second bug was exposed almost by accident, for -M --dmidecode data, there was
a missing field and also a missing is set test on that field that led to an error
of using undefined value in string comparison. This was strictly speaking 2 bugs,
both very old, from 2.9 first rewrite, one failing to set/get the value, and the
other failing to test if the value was set before using it.
Fixes:
1. There were a few glitches in help menu and man page related to -L option, those
are corrected.
INTERNAL CODE CHANGES:
1. removed bug inducing splice use in some cases, and added parens to splice to make
it fit the new way of with perl builtins, when taking 2 or more arguments, use parens.
2. Found many more instances to add -> dereferencing operator. I have to say, not
doing that consistently made the code much harder to read, and created situations
where it's somewhat ambiguous what item belongs to what, with everything consistently
-> operator run, the code is more clear and obvious, and some of the hacks I'd added
because of the lack of clarity were also removed.
3. Removed explicit setting of hash references with null value, that was done out
of failure to use -> operators which clearly indicate to Perl and coder what is
happening, so those crutches were removed. Also got rid of unnecessary array
priming like: my @array = (); Some of these habits came from other languages,
but in Perl, declaring my @array means it's an array that is null, and you don't
need to do a further (). @array = () is obviously fine for resetting arrays in
loops or whatever, but not in the initial declaration.
2020-12-17 22:51:11 +00:00
|
|
|
\fBDevice\-[xx] [name/id] type: [LUKS|Crypto|bcache]:\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-m \fR, \fB\-\-memory\fR
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
Memory (RAM) data. Does not display with \fB\-b\fR or \fB\-F\fR unless you use
|
|
|
|
|
\fB\-m\fR explicitly. Ordered by system board physical system memory array(s)
|
|
|
|
|
(\fBArray\-[number]\fR), and individual memory devices (\fBDevice\-[number]\fR).
|
|
|
|
|
Physical memory array data shows array capacity, number of devices supported,
|
|
|
|
|
and Error Correction information. Devices shows locator data (highly variable in
|
|
|
|
|
syntax), type (eg: \fBtype: DDR3\fR)size, speed.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Note: \fB\-m\fR uses \fBdmidecode\fR, which must be run as root (or start
|
|
|
|
|
\fBinxi\fR with \fBdoas/sudo\fR), unless you figure out how to set up doas/sudo
|
|
|
|
|
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.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
Note: If \fB\-m\fR is triggered RAM available/used report will appear in this
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
section, not in \fB\-I\fR or \fB\-tm\fR items.
|
|
|
|
|
|
|
|
|
|
Because \fBdmidecode\fR data is extremely unreliable, inxi will try to make
|
|
|
|
|
best guesses. If you see \fB(check)\fR after the capacity number, you should
|
|
|
|
|
check it with the specifications. \fB(est)\fR is slightly more reliable, but
|
|
|
|
|
you should still check the real specifications before buying RAM. Unfortunately
|
|
|
|
|
there is nothing \fBinxi\fR can do to get truly reliable data about the system
|
|
|
|
|
RAM; maybe one day the kernel devs will put this data into \fB/sys\fR, and make
|
|
|
|
|
it real data, taken from the actual system, not dmi data. For most people, the
|
|
|
|
|
data will be right, but a significant percentage of users will have either a
|
|
|
|
|
wrong max module size, if present, or max capacity.
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
Under dmidecode, \fBSpeed:\fR is the expected speed of the memory
|
|
|
|
|
(what is advertised on the memory spec sheet) and \fBConfigured Clock Speed:\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
is what the actual speed is now. To handle this, if speed and configured speed
|
|
|
|
|
values are different, you will see this instead:
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\fBspeed: spec: [specified speed] MT/s actual: [actual] MT/s\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
Also, if DDR, and speed in MHz, will change to: \fBspeed: [speed] MT/s
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
([speed] MHz)\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds:
|
|
|
|
|
\fBnote: check\fR. Sample:
|
|
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBMemory:
|
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 21:18:45 +00:00
|
|
|
System RAM: total: 32 GiB note: est. available: 31.38 GiB
|
|
|
|
|
used: 20.65 GiB (65.8%)
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
Array\-1: capacity: N/A slots: 4 note: check EC: N/A
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
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)
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
actual: 61910 MT/s (30955 MHz) note: check
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
Device\-3: DIMM_B1 type: DDR3 size: 8 GiB speed: 1600 MT/s (800 MHz)
|
|
|
|
|
Device\-4: DIMM_B2 type: DDR3 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
actual: 2 MT/s (1 MHz) note: check\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.fi
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
See \fB\-\-memory\-modules\fR and \fB\-\-memory\-short\fR if you want a
|
|
|
|
|
shorter report.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
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 21:18:45 +00:00
|
|
|
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.
|
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 18:59:56 +00:00
|
|
|
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
.TP
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
.B \-\-memory\-modules\fR, \fB\-\-mm\fR
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
Memory (RAM) data. Show only RAM arrays and modules in Memory report.
|
|
|
|
|
Skip empty slots. See \fB\-m\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
.TP
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
.B \-\-memory\-short\fR, \fB\-\-ms\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
Memory (RAM) data. Show a one line RAM report in Memory. See \fB\-m\fR.
|
|
|
|
|
|
|
|
|
|
Sample: \fBReport: arrays: 1 slots: 4 modules: 2 type: DDR4\fR
|
|
|
|
|
|
New version, new tarball, new man page. Finally, after all these years, initial memory/ram
support. This feature requires dmidecode, and usually that needs to be run as root.
Significantly improved dmidecode error handling and output, and have as 2.1.90 testing/initial
release basic ram data.
In subsequent releases, extra info for -x and -xx and -xxx will be added as well to the output.
For those who want to jump on board early for ram data, update your repos, for those who want to
wait for the full featured version, with -x type data, wait for 2.2.0
And that's that.
2014-08-12 05:26:35 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-M \fR, \fB\-\-machine\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show machine data. Device, Motherboard, BIOS, and if present, System Builder
|
|
|
|
|
(Like Lenovo). Older systems/kernels without the required \fB/sys\fR data can
|
|
|
|
|
use \fBdmidecode\fR instead, run as root. If using \fBdmidecode\fR, may also
|
|
|
|
|
show BIOS/UEFI revision as well as version. \fB\-\-dmidecode\fR forces use of
|
|
|
|
|
\fBdmidecode\fR data instead of \fB/sys\fR. Will also attempt to show if the
|
|
|
|
|
system was booted by BIOS, UEFI, or UEFI [Legacy], the latter being legacy
|
|
|
|
|
BIOS boot mode in a system board using UEFI.
|
|
|
|
|
|
|
|
|
|
Device information requires either \fB/sys\fR or \fBdmidecode\fR. Note that
|
|
|
|
|
\fBother\-vm?\fR is a type that means it's usually a VM, but inxi failed to
|
|
|
|
|
detect which type, or positively confirm which VM it is. Primary VM
|
|
|
|
|
identification is via systemd\-detect\-virt but fallback tests that should also
|
|
|
|
|
support some BSDs are used. Less commonly used or harder to detect VMs may not
|
|
|
|
|
be correctly detected. If you get an incorrect output, post an issue and we'll
|
|
|
|
|
get it fixed if possible.
|
|
|
|
|
|
|
|
|
|
Due to unreliable vendor data, device type will show: desktop, laptop,
|
|
|
|
|
notebook, server, blade, plus some obscure stuff that inxi is unlikely to
|
|
|
|
|
ever run on.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-n \fR, \fB\-\-network\-advanced\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show Advanced Network device information in addition to that produced by
|
|
|
|
|
\fB\-N\fR. Shows interface, speed, MAC ID, state, etc.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-N \fR, \fB\-\-network\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show Network device(s) information, including device driver. With \fB\-x\fR,
|
|
|
|
|
shows Bus ID, Port number.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-nvidia\fR, \fB\-\-nv\fR
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
.br
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
Deprecated. See \fB\-Ga\fR.
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-o \fR, \fB\-\-unmounted\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
Show unmounted partition information (includes UUID and LABEL if available).
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Shows file system type if you have \fBlsblk\fR installed (Linux only). For
|
|
|
|
|
BSD/GNU Linux: shows file system type if \fBfile\fR is installed, and if you
|
|
|
|
|
are root or if you have added to \fB/etc/sudoers\fR (sudo v. 1.7 or newer):
|
2014-04-03 18:35:14 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.B <username> ALL = NOPASSWD: /usr/bin/file (sample)
|
2014-04-03 18:35:14 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
doas users: see \fBman doas.conf\fR for setup.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Does not show components (partitions that create the md\-raid array) of
|
|
|
|
|
md\-raid arrays.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
To show partition labels or UUIDs (when available and relevant), use with
|
|
|
|
|
\fB\-l\fR or\fB \-u\fR.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-p \fR, \fB\-\-partitions\-full\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Show full Partition information (\fB\-P\fR plus all other detected mounted
|
|
|
|
|
partitions).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
To show partition labels or UUIDs (when available and relevant), use with
|
|
|
|
|
\fB\-l\fR or\fB \-u\fR.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-P \fR, \fB\-\-partitions\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
Show basic Partition information.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Shows, if detected: \fB/ /boot /boot/efi /home /opt /tmp /usr /usr/home /var
|
|
|
|
|
/var/tmp /var/log\fR (for android, shows \fB/cache /data /firmware /system\fR).
|
|
|
|
|
If \fB\-\-swap\fR is not used, shows active swap partitions (never shows file
|
|
|
|
|
or zram type swap). Use \fB\-p\fR to see all mounted partitions.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
To show partition labels or UUIDs (when available and relevant), use with
|
|
|
|
|
\fB\-l\fR or\fB \-u\fR.
|
|
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-processes\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-t\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-r \fR, \fB\-\-repos\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
Show distro repository data. Currently supported repo types:
|
|
|
|
|
|
2017-06-29 19:56:23 +00:00
|
|
|
\fBAPK\fR (Alpine Linux + derived versions)
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\fBAPT\fR (Debian, Ubuntu + derived versions, as well as rpm based
|
|
|
|
|
apt distros like PCLinuxOS or Alt\-Linux)
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New version, new man page.
Bugs:
1. Both a fix and a bug, in that inxi had an out of date list of Xorg drivers.
This led to all the newer Intel devices failing to show their drivers in the
Xorg driver lines, like i915, i965, and so on. Updated to full current list of
Xorg drivers. This is not technically a bug since it's simply things that came
into existence after that logic was last updated. But it looks like a bug.
Fixes:
1. Issues #170 and #168 showed a problem with inxi believing it was running in IRC
when Ansible or MOTD started inxi. This is because they are not tty so trip the
non tty flag, which assumes it's in IRC in that case. The fix was to add a
whitelist of known clients based on the parent name inxi discovers while running
inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file
issue reports then not follow them? Who knows.
Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi
which disables the tty test as well. To handle that scenario, that is, when inxi is
not first in the pipe, I added many known terminal client names to the whitelists.
This works in my tests, though the possible terminals, or programs with embedded
terminals, is quite large, but inxi handles most of them automatically. When it
doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
in the meantime.
2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
in some character sets, like greek or russian utf8. The fix was more of a work-around
than a true fix, but inxi now simply checks the weather local time output for wide
characters, and if detected, switches the local date/time format to iso standard,
which is does not contain non ascii characters as far as I can tell. This seemed to
fix the issue.
3. Added iso9660 from excluded file systems for partitions, not sure how inxi
missed that one for so long.
4. See bug 1, expanded and made current supported intel drivers, and a few other
drivers, so now inxi has all the supported xorg drivers again. Updated docs as well
to indicate where to get that data.
Enhancements:
1. As usual, more disk vendor/product ID matches, thanks to linuxlite hardware
database, which never stops providing new or previously unseen disk ids. Latest
favorite? Swissarmy knife maker victorinox Swissflash usb device.
2. Added Elive system base ID.
3. Added Nutyx CARDS repo type.
2019-01-01 05:11:01 +00:00
|
|
|
\fBCARDS\fR (NuTyX + derived versions)
|
|
|
|
|
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
\fBEOPKG\fR (Solus)
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\fBNETPKG\fR (Zenwalk/Slackware)
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBNIX\fR (NixOS + other distros as alternate package manager)
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBPACMAN\fR (Arch Linux, KaOS + derived versions)
|
|
|
|
|
|
|
|
|
|
\fBPACMAN\-G2\fR (Frugalware + derived versions)
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2014-04-04 02:47:08 +00:00
|
|
|
\fBPISI\fR (Pardus + derived versions)
|
2013-10-05 01:40:00 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBPKG\fR (OpenBSD, FreeBSD, NetBSD + derived OS types)
|
|
|
|
|
|
2015-02-16 02:22:32 +00:00
|
|
|
\fBPORTAGE\fR (Gentoo, Sabayon + derived versions)
|
2015-02-16 02:17:58 +00:00
|
|
|
|
|
|
|
|
\fBPORTS\fR (OpenBSD, FreeBSD, NetBSD + derived OS types)
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\fBSBOPKG\fR (Slackware + derived versions)
|
|
|
|
|
|
|
|
|
|
\fBSBOUI\fR (Slackware + derived versions)
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBSCRATCHPKG\fR (Venom + derived versions)
|
|
|
|
|
|
2015-02-16 02:33:41 +00:00
|
|
|
\fBSLACKPKG\fR (Slackware + derived versions)
|
2015-02-16 02:17:58 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\fBSLAPT_GET\fR (Slackware + derived versions)
|
|
|
|
|
|
|
|
|
|
\fBSLPKG\fR (Slackware + derived versions)
|
|
|
|
|
|
New version, man page. Fixes, enhancements, changes.
Thanks:
1. AntiX forums, for testing -C --admin, suggestions, always helpful.
Bugs:
1. Added switch to set @ps_gui, I forgot case where info block was only thing
that used ps_gui (Nitrux kde nomad latte case). This led to no info: data if
other ps_gui switches not activated. Now each block that can use it activates it.
Fixes:
1. To clarify issue #161 added help/man explanation on how to get colors in cases
where you want to preserve colors for piped or redirected output. Thanks fugo.
2. LMDE 3.0 released, slightly different system base handling, so refactored to
add Debian version, see enhancement 2. Tested on some old vm instances, improved
old system Debian system base id, but it's empirical, distro by distro, there is
no rule I can use to automatically do it, sadly.
3. 'Motherboard' sensors field name added, a few small tweaks to sensors. This
was in response to issue #159, which also raised a problem I was not really
aware of, user generated sensor config files, that can have totally random
field names. Longer term solution, start getting data from sys to pad out
lm-sensors data, or to handle cases where no lm-sensors installed.
4. Fixed kwin_11 and kwin_wayland compositor print names, I'd left out the _,
which made it look strange, like there were two compositors or something.
5. Fixed latte-dock ID, I thought the program name when running was latte, not
latte-dock. inxi checks for both now. Thanks Nitrux for exposing that in vm test.
6. Sensors: added in a small filter to motherboard temp, avoid values that are
too high, like SYSTIN: 118 C, filters out to only use < 90 C. Very unlikely a
mobo would be more than 90C unless it's a mistake or about to melt. This may
correct anoymous debugger dataset report from rakasunka.
Enhancements:
1. Added --admin to -v 8 and to --debugger 2x
2. Expanded system base to use Debian version tool, like the ubuntu one, that
lets me match version number to codename. The ubuntu one matches code names to
release dates. Added Neptune, PureOS, Sparky, Tails, to new Debian system base
handler.
3. Big enhancement: --admin -C now shows a nice report on cpu vulnerabilities,
and has a good error message if no data found. Report shows:
Vulnerabilities: Type: [e.g. meltdown] status/mitigation: text explanation.
Note: 'status' is for when no mitigation, either not applicable, or is vulnerable.
'mitigation' is when it's handled, and how. Thanks issue #160 Vascom from Fedora
for that request.
4. The never-ending saga of disk vendor IDs continues. More obscure vendors,
more matches to existing vendors. Thanks linuxlite/linux hardware database
Changes:
1. Reordered usb output, I don't know why I had Hubs and Devices use different
ordering and different -x switch priorities, that was silly, and made it hard to
read.
Now shows:
Device/Hub: bus-id-port-id[.port-id]:device-id info: [product info]
type/ports: [devices/hubs] usb: [type, speed]
-x adds drivers for devices, and usb: speed is now default for devices, same as
Hubs. Why I had those different is beyond me.
The USB ordering is now more sensible, the various components of each
matching whether hub or device.
Unfixable or Won't Fix:
1. Unable to detect Nomad desktop. As far as I can tell, Nomad is only a theme
applied to KDE Plasma, there is no program by that name detectable, only a
reference in ps aux to a theme called nomad.
2. Nitrux system base ID will not work until they correct their /etc/os-release file.
3. Tails live cd for some inexplicable reason uses non standard /etc/os-release
field names, which forces me to either do a custom detection just for them, or for
them to fix this bug. I opted for ignoring it, if I let each distro break standard
formats then try to work around it, the distro ID will grow to be a 1000 lines long
easily. Will file distro bug reports when I find these from now on.
Samples:
This shows the corrected, cleaned up, consistent usb output:
inxi -y80 --usb
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID usb: 1.1
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse usb: 1.1
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse usb: 1.1
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
usb: 2.0
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network usb: 2.0
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
inxi -y80 --usb -xxxz
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
chip ID: 1d6b:0002
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1 chip ID: 03eb:0902
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID driver: cm109,snd-usb-audio interfaces: 4 usb: 1.1
chip ID: 0d8c:000e
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse driver: usbhid,wacom
interfaces: 1 usb: 1.1 chip ID: 056a:0011
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse
driver: hid-generic,usbhid interfaces: 2 usb: 1.1 chip ID: 0d3d:0001
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
driver: N/A interfaces: 1 usb: 2.0 chip ID: 04a9:1909
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network
driver: asix interfaces: 1 usb: 2.0 chip ID: 05ac:1402 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
chip ID: 1d6b:0003
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
chip ID: 1d6b:0002
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
chip ID: 1d6b:0003
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
chip ID: 1d6b:0002
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
chip ID: 1d6b:0003
2018-09-07 20:58:55 +00:00
|
|
|
\fBTCE\fR (TinyCore)
|
|
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
\fBURPMI\fR (Mandriva, Mageia + derived versions)
|
2014-04-04 02:47:08 +00:00
|
|
|
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
\fBXBPS\fR (Void)
|
|
|
|
|
|
2018-03-31 03:12:25 +00:00
|
|
|
\fBYUM/ZYPP\fR (Fedora, Red Hat, Suse + derived versions)
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
More will be added as distro data is collected. If yours is missing please
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
show us how to get this information and we'll try to add it.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
See \fB\-rx\fR, \fB\-rxx\fR, and \fB\-ra\fR for installed package count
|
|
|
|
|
information.
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-R \fR, \fB\-\-raid\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
Show RAID data. Shows RAID devices, states, levels, device/array size,
|
|
|
|
|
and components. See extra data with \fB\-x\fR / \fB\-xx\fR.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
md\-raid: If device is resyncing, also shows resync progress line.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Note: supported types: lvm raid, md\-raid, softraid, ZFS, and hardware RAID.
|
|
|
|
|
Other software RAID types may be added, if the software RAID can be made to
|
|
|
|
|
give the required output.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
The component ID numbers work like this: mdraid: the numerator is the actual
|
|
|
|
|
mdraid component number; lvm/softraid/ZFS: the numerator is auto\-incremented
|
|
|
|
|
counter only. Eg. \fBOnline: 1: sdb1\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
If hardware RAID is detected, shows basic information. Due to complexity
|
|
|
|
|
of adding hardware RAID device disk / RAID reports, those will only be added
|
|
|
|
|
if there is demand, and reasonable reporting tools.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-recommends\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Checks inxi application dependencies and recommends, as well as directories,
|
2018-03-31 03:12:25 +00:00
|
|
|
then shows what package(s) you need to install to add support for each feature.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-s \fR, \fB\-\-sensors\fR
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
Show output from sensors if sensors installed/configured: Motherboard/CPU/GPU
|
|
|
|
|
temperatures; detected fan speeds. GPU temperature when available. Nvidia shows
|
|
|
|
|
screen number for multiple screens. IPMI sensors are also used (root required)
|
|
|
|
|
if present.
|
|
|
|
|
|
|
|
|
|
See Advanced options \fB\-\-sensors\-use\fR or \fB\-\-sensors\-exclude\fR if you
|
|
|
|
|
want to use only a subset of all sensors, or exclude one (currently only for
|
|
|
|
|
\fBlm\-sensors\fR and \fB/sys\fR sourced data).
|
|
|
|
|
|
|
|
|
|
For current Linux, will fallback gracefully to using \fB/sys/class/hwmon\fR as
|
|
|
|
|
sensor data source if \fBlm\-sensors\fR is not installed. You can compare the
|
|
|
|
|
two by using \fB\-\-force sensors\-sys\fR option with \fB\-s\fR.
|
2018-04-04 06:41:06 +00:00
|
|
|
.
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-slots\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
Show PCI slots with type, speed, and status information.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-swap\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-j\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-S \fR, \fB\-\-system\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Show System information: host name, kernel, desktop environment (if in X),
|
|
|
|
|
distro. With \fB\-xx\fR show dm \- or startx \- (only shows if present and
|
|
|
|
|
running if out of X), and if in X, with \fB\-xxx\fR show more desktop info,
|
2018-08-28 23:26:41 +00:00
|
|
|
e.g. taskbar or panel.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-t \fR, \fB\-\-processes\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
[\fBc\fR|\fBm\fR|\fBcm\fR|\fBmc NUMBER\fR] Show processes. If no arguments,
|
|
|
|
|
defaults to \fBcm\fR. If followed by a number, shows that number of processes
|
|
|
|
|
for each type (default: \fB5\fR; if in IRC, max: \fB5\fR)
|
2012-09-15 09:18:08 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Make sure that there is no space between letters and numbers (e.g. write as
|
|
|
|
|
\fB\-t cm10\fR).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2017-06-09 17:14:28 +00:00
|
|
|
.B \-t c\fR
|
2018-03-31 03:12:25 +00:00
|
|
|
\- CPU only. With \fB\-x\fR, also shows memory for that process on same line.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2017-06-09 17:14:28 +00:00
|
|
|
.B \-t m\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- memory only. With \fB\-x\fR, also shows CPU for that process on same line.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
If the \fB\-I\fR or \fB\-m\fR lines are not triggered, will also show the
|
|
|
|
|
system RAM used/total information.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
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 21:18:45 +00:00
|
|
|
See \fB\-m\fR for explanation of \fBSystem RAM:\fR fields and values.
|
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 18:59:56 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2017-06-09 17:14:28 +00:00
|
|
|
.B \-t cm\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- CPU+memory. With \fB\-x\fR, shows also CPU or memory for that process on
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
same line.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-u \fR, \fB\-\-uuid\fR
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
Show partition UUIDs. Use with \fB\-j\fR, \fB\-o\fR, \fB\-p\fR, and \fB\-P\fR
|
|
|
|
|
to show partition labels. Does nothing without one of those options.
|
|
|
|
|
|
|
|
|
|
Sample: \fB\-opju\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-U \fR, \fB\-\-update\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Note \- Maintainer may have disabled this function.
|
2014-04-03 18:28:18 +00:00
|
|
|
|
2017-06-09 17:14:28 +00:00
|
|
|
If inxi \fB\-h\fR has no listing for \fB\-U\fR then it's disabled.
|
2014-04-03 18:28:18 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
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:
|
|
|
|
|
\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
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
to that directory. See \fB\-\-man\fR or \fB\-\-no\-man\fR to force or disable
|
|
|
|
|
man install.
|
2017-01-05 00:23:16 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-usb\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-J\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
.TP
|
2021-08-25 03:39:33 +00:00
|
|
|
.B \-V\fR, \fB\-\-version\fR
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
inxi full version and license information. Prints information then exits.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-version\-short\fR, \fB\-\-vs\fR
|
|
|
|
|
inxi single line version information. Prints information if not short form
|
|
|
|
|
(which shows version info already). Does not exit unless used without any other
|
|
|
|
|
options. Can be used with normal line options.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-v \fR, \fB\-\-verbosity\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Script verbosity levels. If no verbosity level number is given, 0 is assumed.
|
|
|
|
|
Should not be used with \fB\-b\fR or \fB\-F\fR.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
Supported levels: \fB0\-8\fR Examples :\fB inxi \-v 4 \fR or \fB inxi \-v4\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 0
|
2017-06-09 17:14:28 +00:00
|
|
|
\- Short output, same as: \fBinxi\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 1
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Basic verbose, \fB\-S\fR + basic CPU (cores, type, average clock speed, and
|
|
|
|
|
min/max speeds, if available) + \fB\-G\fR + basic Disk + \fB\-I\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 2
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds networking device (\fB\-N\fR), Machine (\fB\-M\fR) data, Battery
|
|
|
|
|
(\fB\-B\fR) (if available). Same as: \fBinxi \-b\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 3
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds advanced CPU (\fB\-C\fR) and network (\fB\-n\fR) data; triggers
|
|
|
|
|
\fB\-x\fR advanced data option.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 4
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds partition size/used data (\fB\-P\fR) for (if present): \fB/ /home /var/
|
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 18:59:56 +00:00
|
|
|
/boot\fR. Shows full drive data (\fB\-D\fR)
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 5
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds audio device (\fB\-A\fR), memory/RAM (\fB\-m\fR), bluetooth data
|
|
|
|
|
(\fB\-E\fR) (if present), sensors (\fB\-s\fR), RAID data (if present), partition
|
|
|
|
|
label (\fB\-l\fR), UUID (\fB\-u\fR), full swap data (\fB\-j\fR), and short form
|
|
|
|
|
of optical drives.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 6
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds full mounted partition data (\fB\-p\fR), unmounted partition data
|
|
|
|
|
(\fB\-o\fR), optical drive data (\fB\-d\fR), USB (\fB\-J\fR); triggers
|
|
|
|
|
\fB\-xx\fR extra data option.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 7
|
Thanks manjaro user alven for finding a bunch of corner and not so corner case
errors, glitches, documentation oversights, etc.
This is a point release between the coming full CPU refactor and the current
set of bug fixes and issue handlings.
This release also contains the debuggers for the new CPU data logic, which are
important to get this CPU refactor stable and reliable across old/new systems,
different operating systems and platforms.
Wanted to do this intermediate releaase to get the current fixes out, which
make inxi overall better for CPU issues, but do not handle the core requirement
to do a full refactor.
--------------------------------------------------------------------------------
CORRECTION:
1. On release notes for 3.3.08: due to a long delay to get real debugger data
from the person who had the issue, but finally getting it after the release of
3.3.08, there was NO bug in ps wwaux output. Something else was creating the
linewraps, maybe the subshell, it's basically impossible to know since we never
got a real debugger data set, which is the only real way to get the actual same
data inxi will see.
Was it a subshell wrapping the output? We just can't know, nor are we likely to
ever find out.
This highlights very well however why some issues are essentially impossible to
ever fully resolve without the --debug 22 dataset. This bug/fix is definitely in
that class of issues.
It's never good to accuse another program of having a bug when it doesn't, so
sorry to ps authors, no bug or issue exists for ps in this area.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. wiryonolau issue #259 points out that if --tty is used, default IRC filter
rule is still active and on. Because his case appears to be from an autostart
using Bash, which then gives up to find the parent at dash, which then makes
inxi believe it's in an IRC shell client, that issue doesn't appear to be
resolvable.
--------------------------------------------------------------------------------
BUGS:
1. Documentation, help menu and man page showed wmctl instead of wmctrl,
which for someone who reads the help man, leads to command --fake wmctl failing.
Thanks manjaro user alven for finding this typo.
2. For dmidecode cpu data, had global total values for cache that could result
in wrong output values, 2x or more wrong for L1 / L3 cache on linux. Difficulty
is preserving that data for bsd, which in general do not show phys cpu counts,
and thus make showing totals off. Created new '-total' item for each L cache
type, which will handle > 1 cpus, and also can be used to determine if > 1 cpus
present!.
3. Manjaro user pointed out that hub types were wrong, this is because inxi was
using the INTERFACE ID values for hubs instead of the TYPE values. For all other
device types, INTERFACE is correct, but for hubs, we needed TYPE, so fix is to
detect INTERFACE 9/0/0 and if TYPE present for that, swap.
--------------------------------------------------------------------------------
FIXES:
1. For > 1 cpu systems, with dmidecode sourced cpu cache data, can now determine
physical cpu count based on comparing L2 and L2-total values. This means that
when dmidecode is used on BSD for CPU data, inxi may now be able to deduce that
it is a > 1 cpu system.
2. Forgot to set $run{'filter'} to 0 for whitelist start client detection.
3. Going along with bug 3, changed 'Full speed (or root) hub' to:
Full speed or root hub, to make more clear that it's one or the other, or both.
4. For apply_filter(), added test if <superuser required> just return the
string.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug 1, and fix 1, for > 1 cpu systems, will now show for all
cache: items L1: 2x 1.5 MiB (3 MiB), same for L2 and L3. This is far less
confusing than showing the totals without explaining what they are.
2. Going along with 1, now root is not required to show L1 and L3 -Cxx on Linux
as long as the system is reasonably new, about after 2008, and has getconf -a
supported. That support is came in somewhere around 2.10, not sure exactly when.
Debian Etch had it, Sarge did not, Ubuntu 9.10 had it. Tinycore does not have
getconf at all. This will probably be replaced by a more robust full cpu /sys
data tool.
3. Added ht to default short -Cx flag list, that should show, and it's short.
4. Added --no-filter to activate -Z, --filter-override isn't consistent with
other --no-xxx options, even I forgot it. No changes, just another way to use
-Z.
5. For issue #260 added pch as a new sensor output type, it's kind of a builtin
southbridge / northbridge in the CPU die, but it's not a core, and has a
different temp. Will anyone even know what pch is? probably not, but who cares.
--------------------------------------------------------------------------------
CHANGES:
1. No longer showing for > 1 physical cpu systems the sum total of L1/2/3 cache
data. Now shows per cpu L1/L2/L3, and if > 1 cpu, shows for example:
cache: L1: 2x 512 KiB (1024 KiB) L2: 2x 2 MiB (4 MiB) L3: 2x 20 MiB (40 MiB)
For single physical cpu output remains the same:
cache: L1: 576 KiB L2: 3 MiB L3: 16 MiB
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated help/man for L1/L3 cache -Cxx changes.
2. Updated man and help to suggest -Z for --tty.
3. Forgot to note -v 7 adds -f, added to man/help.
--------------------------------------------------------------------------------
CODE:
* Added 'getconf -a' to debugger, that may be usable for cpu cache data, need to
gather data on that to confirm. that's regading issue #257 cache glitches.
2. Removed all * $physical_count for cache data in cpu_properties, that is now
handled by creating string with cpu count, per cpu caches, and total in parens.
3. Added in fallback failure case for the ZFS file system issue exposed by
accident in issue #258 - will now log in debugger the error, so we can try to
find what is going on there, impossible to reproduce until we find what zfs or
more likely, freebsd, changed there. Could be hyper specific, some weird thing
like a person making a zfs device name with space, impossible to guess. Note
that since the freebsd user declined to supply any data to help resolve this
issue, then closed it, we're back where we usually end up with FreeBSD issues,
either a Linux user (or worse, me) willing and able to find the issue and supply
the debugger data required shows up, OR the issue is ignored as valid but
impossible to resolve.
RANT: Note that this also confirmed to me that in order to preserve my own
sanity and not waste endless hours trying to get data, from now on, unless
utterly trivial, if a FreeBSD user refuses to promptly supply the required data,
the issue will be closed with a freebsd-closed-no-data-supplied label, which
means, valid but not possible to solve due to user refusing to help me help
them.
Come on FreeBSD users!! If you want help, and inxi to support your distro, help
me help you!! If not, then why are you even filing an issue in the first place?
Do you expect faeries to spread magic bug / issue fixing faerie dust over inxi
and then activate it with their little wands? This is growing tiresome to be
honest because it's so utterly predictable.
4. Shuffled order of sensor type detections, there was a slim chance that a non
gpu sensor type could have string intel in it, so put the gpu sensors second
to last, before 'main'.
5. Started refactor of cpu core/cache logic. Added feature to cpu_arch, and
changed it to cpu_info since now it gives by vendor/family/model/stepping both
micorarch and cache/core math array returns. Also started refactor to make more
predictable, with increased comments, about what is going on in cpu_properties
to avoid breaking existing correct results.
6. Added to --debug /sys cpu data globber tool, that will help debugging the new
/sys cpu data feature, will let me insert the file data directly into the logic.
7. Added CpuItem::cpu_data_sys() with debuggers, that will now start collecting
user cpu data whenever the debugger is run, though it's not active yet.
8. Set $Data::Dumper::SortKeys = 1; dugh, could have saved big headaches if had
found this before. Makes all keys sorted cleanly, gets rid of random hash sorts.
2021-11-22 20:47:54 +00:00
|
|
|
\- Adds network IP data (\fB\-i\fR), forced bluetooth (\fB\-E\fR), Logical
|
|
|
|
|
(\fB\-L\fR), RAID (\fB\-R\fR), full CPU flags/features (\fB\-f\fR), triggers
|
|
|
|
|
\fB\-xxx\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-04-06 22:52:08 +00:00
|
|
|
.B \-v 8
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
\- All system data available. Adds advanced EDID data (\fB\-\-edid\fR), Repos
|
|
|
|
|
(\fB\-r\fR), PCI slots (\fB\-\-slots\fR), processes (\fB\-tcm\fR), admin
|
|
|
|
|
(\fB\-\-admin\fR). Useful for testing output and to see what data you can get
|
|
|
|
|
from your system.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-w \fR, \fB\-\-weather\fR
|
|
|
|
|
Adds weather line. To get weather for an alternate location, use \fB\-W
|
|
|
|
|
[location]\fR. See also \fB\-x\fR, \fB\-xx\fR, \fB\-xxx\fR options. Please note
|
|
|
|
|
that your distribution's maintainer may chose to disable this feature.
|
New version, new man. Weather explanations, disks, bugs!!
Bugs:
1. For sensors, in some cases, gpu failed to show correctly. This
should be corrected.
Fixes:
1. Made help/man explanations of weather changes more clear.
Particularly in regards to no automated query info. But also for supported
location syntaxes.
2. Some corner cases of null weather data return null and tripped
a null data error. This is corrected.
3. Added city duplicate filter to weather output, this hopefully will
in some cases avoid printing city name twice, depends on weather source.
4. Removed --weather-source option 0, that no longer works so all code was
removed.
5. More deb822 fixes, loosened up even more syntax. That's a poorly designed
config syntax, hard to work with.
Enhancements:
1. Lots of new disk vendors. So many!! Thanks linux-lite hardware database!
switched to a new method of getting disk name/vendor data, now it's a lot easier
to check for new ones.
2. Added fancybar to desktop info.
2019-03-29 21:11:22 +00:00
|
|
|
|
Many small updates, enhancements, bug fixes!!! We've been saving them up!! Here
they are!! Don't wait!!
Thanks mr. mazda for many issue finds, and suggestions.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. Due to unfixable rpm slowdowns, removed package counts for default output for
rpm based systems. We were seeing delays of up to 30+ seconds just to list the
rpm package count, which is absurd, even after the rpm optimizations inxi
already runs. To allow rpm users to get excluded by default for rpm package list
counts, added --pkg flag plus a short message telling them to use that flag to
get the installed package count if they want it.
Changes like this are very unfortunate, but in 2021 for a package manager at
times to require over 30 seconds to generate a trivial installed package list is
just not acceptable. One of the reasons this release was delayed was this was
not an easy decision to make, it's very rare support for a feature is removed
for specific tools due to how badly the tools may perform. Note that whatever
higher level tool is used, like dnf, zypp, it's still the same speed, they all
appear to use the same core engine.
Basically this decision was forced since either inxi looks really bad and slow,
when it's not, or the actual cause was removed from default outputs.
--------------------------------------------------------------------------------
BUGS:
1. Small bug in nfs blacklist for disk used led to nfs used being added, which
leads to silly used percents. This is corrected.
2. If ram vendor ID failed, inxi would delete the part number. Oops. This was
related to the Mushkin failures.
3. Close to a bug, though not one internally, but to users would appear as one:
ZFS does not act as expected, zpool list did not in fact return the pool size,
which I had always assumed to be the case, but in a very strange decision, does
return something very close to the pool size for mirrors, but NOT for z1 or z2
pools, then it returns the total size of the drives that make up the pool. To
call this strange behavior would be an understatement. The fix was to modify the
logic to use zfs list instead to get the size data. This also makes the drive
total report far more accurate, since it lists usable space now for ZFS as was
always intended. The cause of this was simply that I'd always had access to zfs
mirrors, not z1 or z2 arrays.
--------------------------------------------------------------------------------
FIXES:
1. OpenSuse and maybe others use kdm3 for Trinity, not kdm, so dm was failing.
2. Going along with fix 1, made kde version detection more robust so may catch
more fringe / corner cases for kde desktops. These were mainly added to correct
Trinity desktop version detections.
3. Mushkin ram vendor ID was failing, that is or should be corrected.
4. Added in /dev/disk/by-id handlers for zpool components, there are several
variants, wwn-, pci-, scsi-, ata-, but they all map to the real /dev drive IDs.
Failure to unmap these led to failing to match components and get size info
etc for zfs.
5. See DOCUMENTATION: 2, language changes for weather feature abuse.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo
types. Not sure how that one was missed, but there it is. This should tighten
repo reports for dnf/yum/zypp types.
2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for:
penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2.
3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
since xfwm can run in compositing or non compositing mode. But should show
since many users use compositing mode now.
4. Added OpenMediaVault distro ID and systembase handlers.
5. Going along with zfs bug fix 3, using zfs list data for free, size,
allocated. Trying to understand how zfs developers actually thought about this
is nearly impossible so just used what seems to correspond to reality most.
Also shows raw values for zfs data in RAID along with regular ones to make
clear which is which value.
6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
Both vendors finally released some new CPUs and the data became available,
which doesn't always happen quickly.
7. A bunch of new disk vendors and vendor IDs added. Never stops, like the
sands of time, like the ocean waves, like the scuttling crabs scrounding around
in the seaweed in the foam where the outgoing wave left its mark...
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added leftwm keybindinigs to inxi-data.txt desktop/wm section. Updated more
wm in that section as well, and list more info on wms for future reference etc.
Also reorganized and more more readable wm section.
2. Help/Man now make more clear that automated requests or excessive use of the
inxi weather feature are not under any circumstance permitted. There had been
some ambiguity and lack of clarity about what abuse is, now it should be more
clear.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Refactored uptime parser logic, the code and regex was just getting too
messy and difficult to work with and debug, now it works similar to how the
revised BSD parsers run, the regex are pulled apart and made more granular so
a small syntax change ideally won't break the detections as easily.
2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
time I notice that almost invariably stuff done to save lines of code makes
code harder to read as the feature expands, so it's generally worth just
unravelling it so it all stacks and is easy to scan/read. Also removed extra
white space in parens, which is something I'm leaning more towards but it's
not worth fixing all at once so it's just done where it's noticed.
That's using:
if ( /test/ ){
rather than:
if (/test){
I believe using more white space helped with Perl comprehension in the
intermediate stages, but is not required anymore and just looks like extra
whitespace now.
2021-07-12 02:32:13 +00:00
|
|
|
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! Automated or excessive
|
|
|
|
|
use will lead to your being blocked from any further access. This feature is not
|
|
|
|
|
meant for widget type weather monitoring, or Conky type use. It is meant to get
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
weather when you need to see it, for example, on a remote server. If you did not
|
|
|
|
|
type the weather option in manually, it's an automated request.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2013-05-26 03:19:38 +00:00
|
|
|
.TP
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.B \-W\fR, \fB\-\-weather\-location [location_string]\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Get weather/time for an alternate location. Accepts postal/zip code[, country],
|
|
|
|
|
city,state pair, or latitude,longitude. Note: city/country/state names must
|
|
|
|
|
not contain spaces. Replace spaces with '\fB+\fR' sign. Don't place spaces
|
|
|
|
|
around any commas. Postal code is not reliable except for North America and
|
|
|
|
|
maybe the UK. Try postal codes with and without country code added. Note that
|
|
|
|
|
City,State applies only to USA, otherwise it's City,Country. If country name
|
|
|
|
|
(english) does not work, try 2 character country code (e.g. Spain: es;
|
|
|
|
|
Great Britain: gb).
|
|
|
|
|
|
|
|
|
|
See \fIhttps://en.wikipedia.org/wiki/ISO_3166\-1_alpha\-2\fR for current 2
|
|
|
|
|
letter country codes.
|
2014-04-03 18:35:14 +00:00
|
|
|
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
Use only ASCII letters in city/state/country names.
|
|
|
|
|
|
2019-02-08 04:52:41 +00:00
|
|
|
Examples: \fB\-W 95623,us\fR OR \fB\-W Boston,MA\fR OR
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
\fB\-W 45.5234,\-122.6762\fR OR \fB\-W new+york,ny\fR OR \fB\-W bodo,norway\fR.
|
New version, new man. Weather explanations, disks, bugs!!
Bugs:
1. For sensors, in some cases, gpu failed to show correctly. This
should be corrected.
Fixes:
1. Made help/man explanations of weather changes more clear.
Particularly in regards to no automated query info. But also for supported
location syntaxes.
2. Some corner cases of null weather data return null and tripped
a null data error. This is corrected.
3. Added city duplicate filter to weather output, this hopefully will
in some cases avoid printing city name twice, depends on weather source.
4. Removed --weather-source option 0, that no longer works so all code was
removed.
5. More deb822 fixes, loosened up even more syntax. That's a poorly designed
config syntax, hard to work with.
Enhancements:
1. Lots of new disk vendors. So many!! Thanks linux-lite hardware database!
switched to a new method of getting disk name/vendor data, now it's a lot easier
to check for new ones.
2. Added fancybar to desktop info.
2019-03-29 21:11:22 +00:00
|
|
|
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
DO NOT USE THIS FEATURE FOR AUTOMATED WEATHER UPDATES! Automated or excessive
|
|
|
|
|
use will lead to your being blocked from any further access. This feature is not
|
|
|
|
|
meant for widget type weather monitoring, or Conky type use. It is meant to get
|
|
|
|
|
weather when you need to see it, for example, on a remote server. If you did not
|
|
|
|
|
type the weather option in manually, it's an automated request.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
.TP
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.B \-\-weather\-source\fR, \fB\-\-ws [unit]\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
[\fB1\-9\fR] Switches weather data source. Possible values are \fB1\-9\fR.
|
|
|
|
|
\fB1\-4\fR will generally be active, and \fB5\-9\fR may or may not be active,
|
|
|
|
|
so check. \fB1\fR may not support city / country names with spaces (even if
|
|
|
|
|
you use the \fB+\fR sign instead of space). \fB2\fR offers pretty good data,
|
|
|
|
|
but may not have all small city names for \fB\-W\fR.
|
New version, new man. Weather explanations, disks, bugs!!
Bugs:
1. For sensors, in some cases, gpu failed to show correctly. This
should be corrected.
Fixes:
1. Made help/man explanations of weather changes more clear.
Particularly in regards to no automated query info. But also for supported
location syntaxes.
2. Some corner cases of null weather data return null and tripped
a null data error. This is corrected.
3. Added city duplicate filter to weather output, this hopefully will
in some cases avoid printing city name twice, depends on weather source.
4. Removed --weather-source option 0, that no longer works so all code was
removed.
5. More deb822 fixes, loosened up even more syntax. That's a poorly designed
config syntax, hard to work with.
Enhancements:
1. Lots of new disk vendors. So many!! Thanks linux-lite hardware database!
switched to a new method of getting disk name/vendor data, now it's a lot easier
to check for new ones.
2. Added fancybar to desktop info.
2019-03-29 21:11:22 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Please note that the data sources are not static per value, and can change any
|
|
|
|
|
time, or be removed, so always test to verify which source is being used for
|
|
|
|
|
each value if that is important to you. Data sources may be added or removed
|
|
|
|
|
on occasions, so try each one and see which you prefer. If you get unsupported
|
|
|
|
|
source message, it means that number has not been implemented.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2014-04-03 17:46:31 +00:00
|
|
|
.TP
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.B \-\-weather\-unit [unit]\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
[\fBm\fR|\fBi\fR|\fBmi\fR|\fBim\fR] Sets weather units to metric (\fBm\fR),
|
|
|
|
|
imperial (\fBi\fR), metric (imperial) (\fBmi\fR, default), imperial (metric)
|
|
|
|
|
(\fBim\fR). If metric or imperial not found,sets to default value, or \fBN/A\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.SH FILTER OPTIONS
|
|
|
|
|
The following options allow for applying various types of filtering to the
|
|
|
|
|
output.
|
|
|
|
|
|
New version, new man. Bug fixes, feature updates.
The main reason to release this earlier than I had hoped was because of the /sys
permission change for serial/uuid file data. The earlier we can get this fix out,
the better for end users, otherwise they will think they have no serial data when
they really do.
FIXES:
1. this bug just came to my attention, apparently the (I assume) kernel people
decided for us that we don't need to see our serial numbers in /sys unless we are
root. This is an unfortunate but sadly predictable event. To work around this
recent change (somewhere between 4.14 and 4.15 as far as I can tell), inxi -M and
-B now check for root read-only and show <root required> if the file exists but
is not user readable. I wish, I really wish, that people could stop changing stuff
for no good reason, but that's out of my control, all I can do is adjust inxi to
this reality. But shame on whoever decided that was a good idea.
This is not technically an inxi bug, but rather a regression, since it's caused
by a change in /sys permissions, but users would see it as a bug so I consider
this an important fix.
Note that the new /sys/class/dmi/id permissions result in various possible things:
1. serial/uuid file is empty but exists and is not readable by user
2. serial/uuid file is not empty and exists and is not readable by user
3. serial/uuid file does not exist
4. serial/uuid file exists, is not empty, and is readable by root
Does this change make your life better? It doesn't make mine better, it makes
it worse. Consider filing a bug report against whoever allowed this regression
is my suggestion.
BUGS:
1. A weather bug could result in odd or wrong data showing in weather output, this
was due to a mistake in how the weather data was assembled internally. This error
could lead to large datastore files, and odd output that is not all correct.
2. More of an enhancement, but due to the way 'v' is used in version numbers,
the program_version tool in some cases could have sliced out a 'v' in the wrong
place in the version string, and also could have sliced out legitimate v values.
This v issue also appeared in bios version, so now the new rule for program_version
and certain other version results is to trim off starting v if and only if it is
followed by a number.
FEATURES:
1. Added in OpenBSD support for showing machine data without having to use dmidecode.
This is a combination of systcl -a and dmesg.boot data, not very good quality data
sources, but it is available as user, and it does work. Note that BIOS systems
are the only ones tested, I don't know what the syntax for UEFI is for the field
names and strings. Coming soon is Battery and Sensors data, from the same sources.
Sadly as far as I know, OpenBSD is the only BSD that has such nice, usable (well,
ok, dmesg.boot data is low quality strings, not really machine safe) data. I
have no new datasets from the other BSDs so I don't know if they have decided to
copy/emulate this method.
2. By request, and this was listed in issue #134, item no. 1, added in weather
switchable metric/imperial output. Also added an option, --weather-unit and
configuration item: WEATHER_UNIT with possible values: cf|fc|c|f. The 2nd of
two in cf/fc goes in () in the output. Note that windspeed is m/s or km/h as metric,
inxi shows m/s as default for metric and (km/h as secondary). Also fixed -w
observation date to use local time formatting. That does not work in -W so it shows
the default value.
3. Updated man to show new WEATHER_UNIT config option, and new --weather-unit
option. Also fixed some other small man glitches that I had missed.
2018-05-11 20:53:26 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-filter \fR, \fB\-\-filter\-override\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-z\fR, \fB\-Z\fR.
|
Big change, cleanup, small bug fixes. Hot, grab it now!!
The new -y 1 feature exposed several small and larger glitches with how sets
of data were constructed in inxi output. See Changes: for list of changes made
to improve or fix these glitches.
These errors and minor output inconsistencies became very obvious when I was
doing heavy testing of -y 1, so I decided to just fix all of them at the same
time, plus it was very hard to make the -y 1 indenter work as expected when the
key values were not being treated consistently.
Note that this completes the set of all possible -y results:
Full -y Options:
1. -y [no integer given] :: set width to a default of 80. this is what you usually
want for forum posts, or for online issue reports, because it won't wrap and be
hard to read. Help us help your users and others!! Teach them to use for example
-Fxzy or -bay for their bug reports. Just add y to whatever collection of arguments
you generally ask for in support forums or issue reports. Highly recommended,
easy to type, and joins cleanly with other letters.
2. -y -1 :: removes line width limits, this can lead to very long lines in some
cases, and removes all auto-wrapping of line widths.
3. -y 1 :: Switch to stacked key: value pairs, with primary data blocks separated
by a blank line. Think dmidecode type output, or other command line sys info tools.
By request, a forum support guy noted it was hard for newbies to understand the
-G values, particularly -Ga when in lines, so this is another way to request
data. WARNING: for lots of data, this gets really long!!! But if you are curious
how inxi actually constructs its data internally, this sort of shows it.
4. -y 80-xx :: set width to 80 or greater. Note you can also set these in
your configurations if you want using the various options supported.
-----------------------------------
Bugs:
1. Once again, no real bugs found beyond a few trivial things I can't remember.
Fixes:
1. When out of X, dm: showed after Console: and often said dm: N/A particularly
on headless servers, which was silly. Now DM: only shows after Console: if
a DM: was actually found. If regular Desktop output, either in X, or via
--display out of X, no changes.
2. There was a pointless sudo test when sudo values are set initially, they
were still running even if --no-sudo was used. Now they don't run in that case.
Enhancements:
1. The biggie, now inxi can output in a similar indented way as something like
dmidecode if you use the -y 1 option. This feature was originally by request,
though the initial request actually just wanted to see it stacked simply,
but that was almost impossible to read for any output reasonably long, so
I made the indentations very dynamic and deep, they go up to 4 levels in,
which is roughly how deep in the inxi sub Categories go. This output format
makes it very easy to see how inxi 'thinks' about its data, how it views
sets, subsets, subsubsets, and subsubsubsets of data.
Note that each data block, as with dmidecode data, is separated by a blank
line. You know what this means!!! Yes, that's right!!! You can parse inxi
output with awk!!, same way legacy bash+gawk inxi used to parse its data!!
Or if your brain just does not like lines of data, you can make it appear in
indented single key: value pairs.
Here you can see for example that 1 Xorg Display has 1 or more Screens,
and each Screen has one or more Monitors. Note that this -Ga data first
appeared in inxi 3.1.00.
Sample [with bug in OpenGL output!, and showing -Ga newer values as well
for dual monitor setup, with one Xorg Screen]:
inxi -aGy1
Graphics:
Device-1: NVIDIA GT218 [GeForce 210]
vendor: Gigabyte
driver: nouveau
v: kernel
bus ID: 09:00.0
chip ID: 10de:0a65
Display: x11
server: X.Org 1.20.8
driver: nouveau
unloaded: fbdev,modesetting,vesa
display ID: :0.0
screens: 1
Screen-1: 0
s-res: 2560x1024
s-dpi: 96
s-size: 677x271mm (26.7x10.7")
s-diag: 729mm (28.7")
Monitor-1: DVI-I-0
res: 1280x1024
hz: 60
dpi: 96
size: 338x270mm (13.3x10.6")
diag: 433mm (17")
Monitor-2: VGA-0
res: 1280x1024
hz: 60
dpi: 86
size: 376x301mm (14.8x11.9")
diag: 482mm (19")
OpenGL:
renderer: N/A
v: N/A
direct render: N/A
2. Refactored and cleaned up print_data(), got rid of some early testing code,
dumped some unnecessary tests, simplified old tests, and optimized the new
indentation logic reasonably well. Hopefully the print_data() will not be
quite as much of a black box now as it was.
3. Even more drive vendors and ID matches!!! The list never ends!! An endless
series of new vendors and IDs of existing vendors sprout up, then float away.
And inxi follows them to the best of its ability. Thanks again to Linux-Lite
hardware database, which help make this ever expanding list possible, since
their users appear to use every disk known to humankind.
Changes:
1. When out of Display, and Console: shows, -S will not show dm: if no
display manager is detected, and if it is detected, it shows DM: since it's
not part of the Console: set of data. If out of X and --display is used to
get Xorg data out of X, it will show Desktop: set of data as normal, at least
it will show the stuff it can find. This resolves the issue where dm: appeared
to be a member of the set of Console: data, instead of either its own thing,
DM:, or a member of the set of Desktop: data.
2. For RAID Devices with sub Array-x: values, Array-x: is capitalized, it used
to be array-x: That was silly.
3. In USB, now Device-x: resets inside each Hub: so that the Device-x: are
numbered starting at 1 within each Hub:. This makes the counter behavior act
the same as it does in for example RAM Array-x: / Device-y:, where each Array-x:
resets Device-y: count to 1. This changes the old default of having Device-x:
not reset, to let you see the total number of devices plugged in or attached
no matter which hub they were plugged into, but the output actually gets
sort of confusing in single key: value pair mode per line.
4. The key: value syntax for weather was changed completely, now it works
like the rest of the features, with Report:... [Forecast:...] Locale:...
and Source:. Locale makes the source of the times and other date related
features, and the location if shown or available, much more obvious. Before
it was never clear if Current Time referred to your local or the remote
time, now it's clearly from the Locale: you specified with -W, or
the default -w local info. Also made Report 1 line if unwrapped, Forecast 1
line if not wrapped, and Locale: 1 line if not wrapped, which makes the output
easier to read.
NOTE: automated weather queries are NOT allowed, if you do it, you will be
banned!! inxi is NOT a desktop weather app!! Don't confuse it with one!!
Weather is just a small service to users who might for example want to check
the weather on a remote system, or something like that, and is not intended
to be used on a routine basis.
5. Cleaned up and re-ordered the --version output. It had some pretty old
contexts in the language, which were removed or cleaned up and brought up to
date. If you're wondering, I roughly use rsync and nano --version as guides
for what to show or not show there.
2020-06-12 07:47:10 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-filter\-label\fR, \fB\-\-filter\-uuid\fR, \fB\-\-filter\-vulnerabilities\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-\-zl\fR, \fB\-\-zu\fR, \fB\-\-zv\fR.
|
Big change, cleanup, small bug fixes. Hot, grab it now!!
The new -y 1 feature exposed several small and larger glitches with how sets
of data were constructed in inxi output. See Changes: for list of changes made
to improve or fix these glitches.
These errors and minor output inconsistencies became very obvious when I was
doing heavy testing of -y 1, so I decided to just fix all of them at the same
time, plus it was very hard to make the -y 1 indenter work as expected when the
key values were not being treated consistently.
Note that this completes the set of all possible -y results:
Full -y Options:
1. -y [no integer given] :: set width to a default of 80. this is what you usually
want for forum posts, or for online issue reports, because it won't wrap and be
hard to read. Help us help your users and others!! Teach them to use for example
-Fxzy or -bay for their bug reports. Just add y to whatever collection of arguments
you generally ask for in support forums or issue reports. Highly recommended,
easy to type, and joins cleanly with other letters.
2. -y -1 :: removes line width limits, this can lead to very long lines in some
cases, and removes all auto-wrapping of line widths.
3. -y 1 :: Switch to stacked key: value pairs, with primary data blocks separated
by a blank line. Think dmidecode type output, or other command line sys info tools.
By request, a forum support guy noted it was hard for newbies to understand the
-G values, particularly -Ga when in lines, so this is another way to request
data. WARNING: for lots of data, this gets really long!!! But if you are curious
how inxi actually constructs its data internally, this sort of shows it.
4. -y 80-xx :: set width to 80 or greater. Note you can also set these in
your configurations if you want using the various options supported.
-----------------------------------
Bugs:
1. Once again, no real bugs found beyond a few trivial things I can't remember.
Fixes:
1. When out of X, dm: showed after Console: and often said dm: N/A particularly
on headless servers, which was silly. Now DM: only shows after Console: if
a DM: was actually found. If regular Desktop output, either in X, or via
--display out of X, no changes.
2. There was a pointless sudo test when sudo values are set initially, they
were still running even if --no-sudo was used. Now they don't run in that case.
Enhancements:
1. The biggie, now inxi can output in a similar indented way as something like
dmidecode if you use the -y 1 option. This feature was originally by request,
though the initial request actually just wanted to see it stacked simply,
but that was almost impossible to read for any output reasonably long, so
I made the indentations very dynamic and deep, they go up to 4 levels in,
which is roughly how deep in the inxi sub Categories go. This output format
makes it very easy to see how inxi 'thinks' about its data, how it views
sets, subsets, subsubsets, and subsubsubsets of data.
Note that each data block, as with dmidecode data, is separated by a blank
line. You know what this means!!! Yes, that's right!!! You can parse inxi
output with awk!!, same way legacy bash+gawk inxi used to parse its data!!
Or if your brain just does not like lines of data, you can make it appear in
indented single key: value pairs.
Here you can see for example that 1 Xorg Display has 1 or more Screens,
and each Screen has one or more Monitors. Note that this -Ga data first
appeared in inxi 3.1.00.
Sample [with bug in OpenGL output!, and showing -Ga newer values as well
for dual monitor setup, with one Xorg Screen]:
inxi -aGy1
Graphics:
Device-1: NVIDIA GT218 [GeForce 210]
vendor: Gigabyte
driver: nouveau
v: kernel
bus ID: 09:00.0
chip ID: 10de:0a65
Display: x11
server: X.Org 1.20.8
driver: nouveau
unloaded: fbdev,modesetting,vesa
display ID: :0.0
screens: 1
Screen-1: 0
s-res: 2560x1024
s-dpi: 96
s-size: 677x271mm (26.7x10.7")
s-diag: 729mm (28.7")
Monitor-1: DVI-I-0
res: 1280x1024
hz: 60
dpi: 96
size: 338x270mm (13.3x10.6")
diag: 433mm (17")
Monitor-2: VGA-0
res: 1280x1024
hz: 60
dpi: 86
size: 376x301mm (14.8x11.9")
diag: 482mm (19")
OpenGL:
renderer: N/A
v: N/A
direct render: N/A
2. Refactored and cleaned up print_data(), got rid of some early testing code,
dumped some unnecessary tests, simplified old tests, and optimized the new
indentation logic reasonably well. Hopefully the print_data() will not be
quite as much of a black box now as it was.
3. Even more drive vendors and ID matches!!! The list never ends!! An endless
series of new vendors and IDs of existing vendors sprout up, then float away.
And inxi follows them to the best of its ability. Thanks again to Linux-Lite
hardware database, which help make this ever expanding list possible, since
their users appear to use every disk known to humankind.
Changes:
1. When out of Display, and Console: shows, -S will not show dm: if no
display manager is detected, and if it is detected, it shows DM: since it's
not part of the Console: set of data. If out of X and --display is used to
get Xorg data out of X, it will show Desktop: set of data as normal, at least
it will show the stuff it can find. This resolves the issue where dm: appeared
to be a member of the set of Console: data, instead of either its own thing,
DM:, or a member of the set of Desktop: data.
2. For RAID Devices with sub Array-x: values, Array-x: is capitalized, it used
to be array-x: That was silly.
3. In USB, now Device-x: resets inside each Hub: so that the Device-x: are
numbered starting at 1 within each Hub:. This makes the counter behavior act
the same as it does in for example RAM Array-x: / Device-y:, where each Array-x:
resets Device-y: count to 1. This changes the old default of having Device-x:
not reset, to let you see the total number of devices plugged in or attached
no matter which hub they were plugged into, but the output actually gets
sort of confusing in single key: value pair mode per line.
4. The key: value syntax for weather was changed completely, now it works
like the rest of the features, with Report:... [Forecast:...] Locale:...
and Source:. Locale makes the source of the times and other date related
features, and the location if shown or available, much more obvious. Before
it was never clear if Current Time referred to your local or the remote
time, now it's clearly from the Locale: you specified with -W, or
the default -w local info. Also made Report 1 line if unwrapped, Forecast 1
line if not wrapped, and Locale: 1 line if not wrapped, which makes the output
easier to read.
NOTE: automated weather queries are NOT allowed, if you do it, you will be
banned!! inxi is NOT a desktop weather app!! Don't confuse it with one!!
Weather is just a small service to users who might for example want to check
the weather on a remote system, or something like that, and is not intended
to be used on a routine basis.
5. Cleaned up and re-ordered the --version output. It had some pretty old
contexts in the language, which were removed or cleaned up and brought up to
date. If you're wondering, I roughly use rsync and nano --version as guides
for what to show or not show there.
2020-06-12 07:47:10 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-host\fR
|
|
|
|
|
Turns on hostname in System line. Overrides inxi config file value (if set):
|
|
|
|
|
|
|
|
|
|
\fBSHOW_HOST='false'\fR \- Same as: \fBSHOW_HOST='true'\fR
|
|
|
|
|
|
|
|
|
|
This is an absolute override, the host will always show no matter what
|
|
|
|
|
other switches you use.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-no\-host\fR
|
|
|
|
|
Turns off hostname in System line. This is default when using \fB\-z\fR,
|
|
|
|
|
for anonymizing inxi output for posting on forums or IRC. Overrides
|
|
|
|
|
configuration value (if set):
|
|
|
|
|
|
|
|
|
|
\fBSHOW_HOST='true'\fR \- Same as: \fBSHOW_HOST='false'\fR
|
|
|
|
|
|
|
|
|
|
This is an absolute override, the host will not show no matter what other
|
|
|
|
|
switches you use.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-z\fR, \fB\-\-filter\fR
|
|
|
|
|
Adds security filters for IP addresses, serial numbers, MAC, location
|
|
|
|
|
(\fB\-w\fR), and user home directory name. Removes Host:. On by default for IRC
|
|
|
|
|
clients.
|
|
|
|
|
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-za\fR, \fB\-\-filter\-all\fR
|
|
|
|
|
Shortcut to trigger \fB\-z\fR, \fB\-\-zl\fR, \fB\-\-zu\fR, \fB\-\-zv\fR. All the
|
|
|
|
|
filters, that is.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-zl\fR, \fB\-\-filter\-label\fR
|
|
|
|
|
Filter partition label names from \fB\-j\fR, \fB\-o\fR, \fB\-p\fR, \fB\-P\fR,
|
|
|
|
|
and \fB\-Sa\fR (root=LABEL=...). Generally only useful in very specialized
|
|
|
|
|
cases.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-zu\fR, \fB\-\-filter\-uuid\fR
|
|
|
|
|
Filter partition UUIDs from \fB\-j\fR, \fB\-o\fR, \fB\-p\fR, \fB\-P\fR, and
|
|
|
|
|
\fB\-Sa\fR (root=UUID=...). Generally only useful in very specialized cases.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new tarball, new man page. Unless disabled by distribution maintainers, offers
weather -w option. With -x, -xx-, -xxx, shows more information. Basic line is just weather
and system time there. -x adds time zone, which is useful for servers, particurly web servers.
-x also adds wind speed. -xx adds humidity and barometric pressure. -xxx adds a possible new line,
if data is available, heat index, wind chill, and dew point.
-xxx also adds a line for location (blocked by irc/-z) / weather observation time.
-z filter applies as usual to location data, removes it in irc by default. -Z overrides override.
The api this uses is probably going to be dropped at some point, so this is just going to work
while it works, then it will need to be updated at some point, so don't get very attached to it.
Also adds option to, with -w: -! location=<location string>
This lets users send an alternate location using either <city,state> or <postal code>
or <latitude,longitude> (commas for city,state and latitude,longitude are not optional, and the order
must be as listed.
If There is a developer flag if distro maintainers do not want this enabled, simply set:
B_ALLOW_WEATHER='false'
before packaging and the weather feature will be disabled.
2013-05-18 02:04:29 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-\-zv\fR, \fB\-\-filter\-v\fR, \fB\-\-filter\-vulnerabilities\fR
|
|
|
|
|
Filter Vulnerabilities report from \fB\-Ca\fR. Generally only useful in very
|
|
|
|
|
specialized cases.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-Z \fR, \fB\-\-filter\-override \fR, \fB\-\-no\-filter\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Absolute override for output filters. Useful for debugging networking
|
2018-03-31 03:12:25 +00:00
|
|
|
issues in IRC for example.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.SH OUTPUT CONTROL OPTIONS
|
|
|
|
|
The following options allow for modifying the output in various ways.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c \fR, \fB\-\-color\fR \fR[\fB0\fR\-\fB42\fR]
|
|
|
|
|
Set color scheme. If no scheme number is supplied, 0 is assumed.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c \fR[\fB94\fR\-\fB99\fR]
|
|
|
|
|
These color selectors run a color selector option prior to inxi starting
|
|
|
|
|
which lets you set the config file value for the selection.
|
|
|
|
|
|
|
|
|
|
NOTE: All configuration file set color values are removed when output is
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
piped or redirected. You must use the explicit runtime \fB\-c [color number]\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
option if you want color codes to be present in the piped/redirected output.
|
|
|
|
|
|
|
|
|
|
Color selectors for each type display (NOTE: IRC and global only show safe
|
|
|
|
|
color set):
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 94\fR
|
|
|
|
|
\- Console, out of X.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 95\fR
|
|
|
|
|
\- Terminal, running in X \- like xTerm.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 96\fR
|
|
|
|
|
\- GUI IRC, running in X \- like XChat, Quassel,
|
|
|
|
|
Konversation etc.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 97\fR
|
|
|
|
|
\- Console IRC running in X \- like irssi in xTerm.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 98\fR
|
|
|
|
|
\- Console IRC not in X.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-c 99\fR
|
|
|
|
|
\- Global \- Overrides/removes all settings.
|
|
|
|
|
|
|
|
|
|
Setting a specific color type removes the global color selection.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-export [json|screen|xml]\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-\-output\fR.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-indent [11\-xx]\fR
|
|
|
|
|
Change primary wide indent width. Generally useless. Only applied if output
|
|
|
|
|
width is greater than max wrap width (see \fB\-\-max\-wrap\fR). Use
|
|
|
|
|
configuration item \fBINDENT\fR to make permanent.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-indents [0\-10]\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Change primary wrap mode, second, and \fB\-y1\fR level indents. First indent
|
|
|
|
|
level only applied if output width is less than max wrap width (see
|
|
|
|
|
\fB\-\-max\-wrap\fR). 0 disables all wrapped indents and all second level
|
|
|
|
|
indents. Use configuration item \fBINDENTS\fR to make permanent.
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-limit [\-1 \- x]\fR
|
|
|
|
|
Raise or lower max output limit of IP addresses for \fB\-i\fR. \fB\-1\fR
|
|
|
|
|
removes limit.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-max\-wrap\fR, \fB\-\-wrap\-max [integer]\fR
|
|
|
|
|
Overrides default or configuration set line starter wrap width value. Wrap max
|
|
|
|
|
is the maximum width that inxi will wrap line starters (e.g. \fBInfo:\fR) to
|
|
|
|
|
their own lines, with data lines indented default 2 columns (use
|
|
|
|
|
\fB\-\-indents\fR to change).
|
|
|
|
|
|
|
|
|
|
If terminal/console width or \fB\-\-width\fR is less than wrap width, wrapping
|
|
|
|
|
of line starter occurs. If \fB80\fR or less, no wrapping will occur. Overrides
|
|
|
|
|
internal default value (110) and user configuration value \fBMAX_WRAP\fR.
|
|
|
|
|
|
|
|
|
|
.TP
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.B \-\-output\fR, \fB \-\-export [json|screen|xml]\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Change data output type. Requires \-\-output\-file if not \fBscreen\fR.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
See this page \fIhttps://smxi.org/docs/inxi-json-xml-output.htm\fR BEFORE you
|
|
|
|
|
post an issue about not understanding, or being unable to use, the output
|
|
|
|
|
format! That gives a fairly complete explanation of what the output means, and
|
|
|
|
|
how to work with it. It is not a tutorial, and it will not teach you to program,
|
|
|
|
|
if you don't know how to work with json/xml structures using a proper language,
|
|
|
|
|
then this feature is not meant for you.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.B \-\-output\-file, \fB \-\-export\-file [full path to output file|print]\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
The given directory path must exist. The directory path given must exist,
|
|
|
|
|
The \fBprint\fR options prints to stdout.
|
|
|
|
|
Required for non\-screen \fB\-\-output\fR formats (json|xml).
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-partition\-sort [dev\-base|fs|id|label|percent\-used|size|uuid|used]\fR
|
|
|
|
|
Change default sort order of partition output. Corresponds to
|
|
|
|
|
\fBPARTITION_SORT\fR configuration item. These are the available sort options:
|
|
|
|
|
|
|
|
|
|
\fBdev\-base\fR - \fB/dev\fR partition identifier, like \fB/dev/sda1\fR.
|
|
|
|
|
Note that it's an alphabetic sort, so \fBsda12\fR is before \fBsda2\fR.
|
|
|
|
|
|
|
|
|
|
\fBfs\fR \- Partition filesystem. Note that sorts will be somewhat random if
|
|
|
|
|
all filesystems are the same.
|
|
|
|
|
|
|
|
|
|
\fBid\fR \- Mount point of partition (default).
|
|
|
|
|
|
|
|
|
|
\fBlabel\fR \- Label of partition. If partitions have no labels,
|
|
|
|
|
sort will be random.
|
|
|
|
|
|
|
|
|
|
\fBpercent\-used\fR - Percentage of partition size used.
|
|
|
|
|
|
|
|
|
|
\fBsize\fR \- KiB size of partition.
|
|
|
|
|
|
|
|
|
|
\fBuuid\fR \- UUID of the partition.
|
|
|
|
|
|
|
|
|
|
\fBused\fR \- KiB used of partition.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-separator\fR, \fB\-\-sep [character(s)]\fR
|
|
|
|
|
Change the default output key: value separator \fB:\fR to something else. Make
|
|
|
|
|
permanent with configuration item \fBSEP2_CONSOLE\fR.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-wrap\-max [integer]\fR
|
|
|
|
|
.br
|
|
|
|
|
See \fB\-\-max-wrap\fR.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-y\fR, \fB\-\-width [integer]\fR
|
|
|
|
|
This is an absolute width override which sets the output line width max.
|
|
|
|
|
Overrides \fBCOLS_MAX_IRC\fR, \fBCOLS_MAX_NO_DISPLAY\fR, \fBCOLS_MAX_CONSOLE\fR
|
|
|
|
|
configuration items, or the actual widths of the terminal.
|
|
|
|
|
|
|
|
|
|
* \fB\-y\fR \- sets default width of 80 columns.
|
|
|
|
|
.br
|
This release fixes another very long standing bug, which I was not sure was an
inxi or a Konversation bug, which made tracking it down very difficult. Special
thanks to argonel of Konversation for helping solve this problem, or at least,
for directing my attention towards the likely cause area, and away from wrong
ideas. The bug was that inxi simply did not run in Konversation, it would exit
with error when run with /cmd or /inxi via symbolic links.
This may not seem like a huge deal to many of you, but the actual history of
inxi was directly linked to user support in mainly Konversation, so this feature
not working I have alwyas found extremely annoying, but I could never figure out
why it wasn't workiing, and didn't really know where to start until Argonel
helped narrow it down to a specific Konversation function in inxi. At which
point tracking down the real bug was fairly easy. Since testing in IRC is always
a key test point for inxi features and releases, not working in my main GUI IRC
client forced me to use CLI clients like irssi, via /exec -o inxi.
There was a secondary cause of failure, which was missing a key qdbus package,
which made figuring this one out a two step process.
So inxi is once again working in all areas, with no known significant failure
areas beyond known issues that have no current solution, or which I don't feel
like doing.
But possibly more important, a goal I have had for a while now of doing long
needed code refactors, bug fixes, without huge new code blocks or features
adding new future fixes and bugs, has been slowly happening.
This was quite important, because inxi's codebase and logic is so complex and
large now that at some point, it required rest and cleanup and corrections,
without continuously adding new code and logic, which would then trigger new
fixes and bugs. In other words, the code is taking a long needed, and well
deserved, breather, to recover after huge increases in the overall LOC and
feature sets.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. No known way to detect that the system might be Wayland for the Graphics:..
API: fixes, unless Xwayland is installed if the wayland protocol detections
failed, which they often do in console. Not practical to look for all compositor
variants on system to determine if it could be Wayland if not X or Xvesa, so
that one will just be what it is, which is fine, definitely better than it was
before. Note this is only an issue if in Console, no Display. Note that if inxi
is run as root, Wayland data also usually fails, even in Display.
--------------------------------------------------------------------------------
BUGS:
1. Another corner case monitor position issue, applied fallback primary monitor
rule when a primary monitor had already been located. This is corrected via a
graphics global $b_primary which once set will disable this fallback feature.
Objectively, the fallback feature should just be removed. The test is if that
monitor is not primary, and if position is 0x0, then assume primary, without
verifying no primary had been located yet.
2. A super old bug, in current konversation, was failing to trip the konvi
detections, which then resulted in not stripping off the first two args in
@ARGV, which then resulted in bad args being passed to inxi on konvi start,
which then resulted in silent failing. Many thanks to argonel of #konversation
for the patience to help me figure out what was going on with this bug. He's
been a Konversation developer probably longer than I've been doing inxi.
Cause was very tricky and subtle, the ps aux path for konvi had changed
slightly, not the path, but the pattern, it used to be:
konversation -session [sessin id]
but it's changed to:
konversation -qwindowtitle Konversation
or just plain:
konversation as line ending.
This led to failure to find konvi running, which then made the konvi ids fail.
Also, this would not work if the qdbus-qt5 package was not installed, or other
distros might have that packaged differently. Because of these dual causes, I
was simply unable to figure out what was going on for many years. I suspect this
stopped working with KDE 5/QT 5, but I'm not sure.
3. Used wrong key names for some ZFS tests and fallbacks, those could have led
to failures though very difficult to test and verify this. Also see fix 5, which
of course also looks like a bug, acts like one, but was actually due to a new
use of /dev/disk/by-partuuid for ZFS components in Ubuntu which inxi had not
seen before.
--------------------------------------------------------------------------------
FIXES:
1. Alternate ps IDs for appimage detection (try appimagelauncher), alternate
paths for possible appimage storage locations (also try ~/.appimage/*). File
names might be *.appimage or *.AppImage, probably other variants too.
2. Going along with Change 1, made tests more granular for missing graphics API
type data. Also updated messages to be more correct and clear, in and out of
display. This corrects an issue I'd seen but never resolved, which was on
headless systems showing this message:
Message: GL data unavailable in console. Try -G --display
Now the tests are far more granular, and only show that if glxinfo is installed,
and also shows specific messages if glxinfo not installed, but X/Xorg present,
or, for Wayland, if Xwayland present. These all get their own specific messages
now, and generally will also show which API is being used, or API: N/A if
nothing is detected, as in the case of a headless system with no X, Wayland,
etc.
3. Github issue #275 on of all things Microsoft WSL environment, has a small
glitch with undefined display hz, but otherwise inxi seems to work in that
environment, albeit missing many data types!
4. Made tests for konversation more robust, including test for
$ENV{'PYTHONPATH'} containing konversation in path, which I believe will work
for all new Konversations (KDE 5 and newer), and be much faster. The previous
tests are now more robust and less prone to failure, and only activate when
PYTHONPATH is not present with konversation string present as well.
5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs,
which can lead to wrong usable disk total size report, along with failure
to show components. Thanks delanym, issue #276 for reporting this problem, which
also exposed some harder to trigger bugs in ZFS (Bug 3).
6. Exposed by issue #276, case where line was wrapping value when value was too
short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words
trigger to enable wrapping of value, but noticed that if length of line was
exactly max-width, not > or <, it might vanish.
7. Case where no X or GPU drivers found, but dri driver detected, was not
showing, now does.
8. OpenRC is the init system in some cases, that is: readlink /sbin/init >
/sbin/openrc-init, where /proc/1/comm == init. Was showing only as OpenRC rc
type, which wasn't actually correct.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New nvidia gpu product ids for Turing, Ampere, Lovelace, Hopper. New Intel
GPU ids.
2. Added Zinc to systembase/distro, needs slightly special handling to get both
names right. Also added Tuxedo, which could use existing methods.
3. Added dpkg tool nala, which is sort of a CLI front end for apt, zinc uses it,
but it's also in Debian main package pool. Also deb-get, which is another zinc
thing for package management.
4. Full support for dinit: version, dinitctl w/status in ServiceData
4. Added initial support for init systems: 31init (31 line C program, no
--version), Hummingbird (unknown if -v/--version).
5. A few new CPU arch ids (new Intels).
--------------------------------------------------------------------------------
CHANGES:
1. Going somewhat along with the change in Audio to call ALSA a Sound API
instead of a sound server, changed key name OpenGL: to API: OpenGL in Graphics.
Also for EGL wayland, calling that the api too.
https://en.wikipedia.org/wiki/OpenGL
This conforms more closely to how these things are defined. Note that once
again, a value had been used as a key name, which almost always indicates a
failure to understand something about the core tech.
2. Changed wrapping of values from 3 words or more to 3 or more words AND length
> 24 characters. Saw example of:
.... used: 28.45 GiB
(4.5%)
which isn't desirable.
3. Changed minimum wrap to 60 columns, the new wrapper features are working so
well that if users want output that short, it will usually work fine, except of
course for very long word strings like a kernel name or parameter.
Note that this does not truncate long 'words' that might be wrapped, or going
along with Change 2, long 'sentences' of 2 words, those will always appear on
the same line regardless. For 'sentences' of 3 or more words, however, it goes
word by word, so it could well wrap after the first word, and so on. Obviously,
a 24 or fewer character value will never be wrapped, which was the intended
correction of change 2.
4. Going with Fix 8, OpenRc is an init system when it owns /proc/1/comm, had not
realized that /proc/1/comm == init can map to dinit, openrc as init. Now will
only show OpenRc as rc: type if not init as well.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updates in man for Change 1.
2. Added to docs/inxi-graphics.txt good quote re EGL/GBM, as well as VBE/GOP for
vesa. Trying to find docs where they actually say clearly it's an API is
remarkably difficult.
3. Man page, added note about Konversation requiring qdbus-qt5 (Debian+),
qt5-qttool (RHEL+/SUSE+), qt-tools (Arch+) for inxi to work inside it. Also
updated smxi.org/docs/inxi-usage.txt to note requirements for Konversation use
and setup.
4. Man, help, changed min width for -y/--width from 80 to 60.
5. docs/inxi-values.txt updated for --cygwin, --wsl fake OS type switches. Not
technically the OS, more the environment, but close enough.
6. docs/inxi-init.txt updated for new init types.
--------------------------------------------------------------------------------
CODE:
1. Refactored tools/gpu_ids.pl to correct and enhance some features.
2. Renamed functions and sections to better reflect that the display interface
is an API, this makes stuff less odd internally, and makes the function/variable
names correspond better to what the stuff really is.
3. Commented out kde konversation data source config collector, that logic looks
like it never worked, and couldn't work, since it never actually located
inxi.conf files, just paths to the data directories.
4. Expanded release.pl to handle acxi docs as well, makes it all consistent and
a lot easier to do long term.
5. Fake --wsl WSL switch, not really used, but in case.
6. Changed $b_cygwin to $windows{'cygwin'} and added $windows{'wsl'}.
7. Added -WSL to debugger string generator once WSL type is detected.
8. Refactored init, runlevel functions get_init_data() (now InitData::get()),
get_runlevel_data() (now InitData::get_runlevel()), get_runlevel_default() (now
InitData::get_runlevel_default()) into one package/class: InitData. This should
have been done a long time ago, to follow the general rule "if > 1 functions for
a tool refactor it into a class/package" for when to create a package/class
internally.
9. Completed gpu_ids.pl, now outputs the full hash set per item, so entire
blocks can be copied/pasted over. Something of a pain to get comments included,
which aren't strictly necessary in pinxi itself, but they do help read the
hashes for gpu data.
2022-10-31 22:47:31 +00:00
|
|
|
* \fB\-y [60-xxx]\fR \- sets width to given number. Must be 60 or more.
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
|
|
|
|
* \fB\-y 1\fR \- switches to a single indented key/value pair per line, and
|
|
|
|
|
removes all long line wrapping (similar to \fBdmidecode\fR output). Not
|
|
|
|
|
recommended for use with \fB\-Y\fR;
|
|
|
|
|
.br
|
|
|
|
|
* \fB\-y \-1\fR \- removes width limits (if assigned by configuration items).
|
|
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
.br
|
|
|
|
|
\fBinxi \-Fxx \-y 130\fR
|
|
|
|
|
.br
|
|
|
|
|
\fBinxi \-Fxxy\fR
|
|
|
|
|
.br
|
|
|
|
|
\fBinxi \-bay1\fR
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-Y\fR, \fB\-\-height\fR, \fB\-\-less [\-3\-[integer]\fR
|
|
|
|
|
Control output height. Useful when in console, and scrollback not available.
|
|
|
|
|
Breaks output flow based on values provided.
|
|
|
|
|
|
|
|
|
|
* \fB\-Y 0\fR or \fB\-Y\fR \- Set default max height to terminal height.
|
|
|
|
|
.br
|
|
|
|
|
* \fB\-Y [1\-xxx]\fR \- set max output block height height in lines.
|
|
|
|
|
.br
|
|
|
|
|
* \fB\-Y \-1\fR \- Print out one primary data item block (like \fBCPU:\fR,
|
|
|
|
|
\fBSystem:\fR) at a time. Useful for very long outputs like \fB\-Fa\fR,
|
|
|
|
|
\fB\-v8\fR, etc. Not available for \fB\-h\fR.
|
|
|
|
|
.br
|
|
|
|
|
* \fB\-Y \-2\fR \- Do not disable output colors when redirected or piped to
|
|
|
|
|
another program. Useful if piping output to \fBless \-R\fR for example. This
|
|
|
|
|
does not limit the height otherwise since the expectation it is being piped to
|
|
|
|
|
another program like \fBless\fR which will handle that.
|
|
|
|
|
.br
|
|
|
|
|
* \fB\-Y \-3\fR \- Restore default unlimited output lines if \fBLINES_MAX\fR
|
|
|
|
|
configuration item set.
|
|
|
|
|
|
|
|
|
|
Recommended to use the following for very clean up and down scrollable output
|
|
|
|
|
out of display, while retaining the color schemes, which are normally removed
|
|
|
|
|
with piping or redirect:
|
|
|
|
|
|
|
|
|
|
\fBpinxi \-v8Y \-2 | less \-R\fR
|
|
|
|
|
|
|
|
|
|
Note: since it's not possible for inxi to know how many actual terminal lines
|
|
|
|
|
are being used by terminal wrapped output, with \fB\-y 1\fR , it may be better
|
|
|
|
|
in general to use a fixed height like:
|
|
|
|
|
|
|
|
|
|
\fB\-y 1 \-Y 20\fR instead of: \fB\-y 1 \-Y\fR
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH EXTRA DATA OPTIONS
|
2018-04-06 22:52:08 +00:00
|
|
|
These options can be triggered by one or more \fB\-x\fR.
|
|
|
|
|
Alternatively, the \fB\-v\fR options trigger them in the following
|
|
|
|
|
way: \fB\-v 3\fR adds \fB\-x\fR;
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
\fB\-v 6\fR adds \fB\-xx\fR; \fB\-v 7\fR adds \fB\-xxx\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
These extra data triggers can be useful for getting more in\-depth
|
|
|
|
|
data on various options. They can be added to any long form option list,
|
2018-03-31 03:12:25 +00:00
|
|
|
e.g.: \fB\-bxx\fR or \fB\-Sxxx\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
There are 3 extra data levels:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
\fB\-x\fR, \fB\-xx\fR, \fB\-xxx\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
OR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
\fB\-\-extra 1\fR, \fB\-\-extra 2\fR, \fB\-\-extra 3\fR
|
2012-09-15 09:18:08 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
The following details show which lines / items display extra information for
|
|
|
|
|
each extra data level.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-10-19 19:43:26 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-A\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds (if available and/or relevant) \fBvendor:\fR item, which shows specific
|
|
|
|
|
vendor [product] information.
|
New version, new man. Fixes, stitches, and returns!!
Bugs:
1. As a fix (3), failure to handle spaces in mount source names. More of a fix than
a bug, since it was an old issue #63.
2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data
tripping null data or unreadable file errors, but I'll call those bugs since they
look like bugs to end users. See Fixes for more.
3. See Fix 4, this is sort of a bug, inxi failed to return expected values on
success/failure.
Fixes:
1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented
internally. This is now corrected.
2. Apple OSX was returning errors, those were fixed.
3. Finally handled ancient issue #63, support now there for spaces in remote source
name. This means that both spaces in source block name, and mount point name, are
in theory both handled now. This was also to fix an osx issue #164 despite the
fact that technically I do not support osx beyond fixing errors, but since in this
case the issue was a long standing one, I fixed it for everything.
4. Big fix, I'd completely left undone proper unix type error number returns in
inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi
returns integer success/error numbers as expected.
5. OSX xml based version info broke, of course, naturally it would, so I added in
an osx fallback where if no distro version detected, use fallback unix method, which
is what all the other unices use.
6. Along with space in source name, fixed mapped handling a bit more too for
partitions.
6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure
how I'd missed those for so long.
7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a,
sigh, human readable default format, in M, so to handle this for all bsds, I had
to make a dynamic column detection for avm and fre, and use those after, and also
i had to add in a M detection, if found, *1024 and strip out M, sigh.
8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks
does not always use the same order in comma separated list, saw user case where
the first item after : was the MB size, not the second. Made detection dynamic.
9. Due to Android case, found types where no cpu speed data was found, no max speed
at least, which tripped an error due to null data for ARM, this is now handled,
now cpu speed min/max read permissions in /sys are checked first before trying to
read, and default failures are better handled.
10. On man page, added in clarification of the moving of Memory: item from Info:
line to ram Memory: line, explaining when it appears where. I do not removing the
item from -I, I may revert that change, I find it non-intuitive to move that
around.
Enhancements:
1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this
closes issues #166 #165 #162
2. Improved documentation a bit to avoid ambiguity re how to get colors in output.
That handles issue #161, thanks fugo for the nudge to improve the documentation.
3. First inxi on Android tests, using termux, which has a debian based apt
type installer, got inxi running on at least two devices, including pixel2, but
discovered that apparently as of android 5, /sys is now locked up in terms of
wildcard reads, but further analysis is required, but as of now, inxi works in
termux, but fails to get any Device data for A, G, or N. Thus it also fails to match
IF to Device, so none of the IP data shows up. The latter will probably be fixed
since Android has ip and ifconfig already, or termux does, but so far I found no
way to get device data for ARM in Android 5.x and greater (checked on
android 7 and 9 in real phones).
4. More disk vendors!! thanks linuxlite / linux hardware database for offering an
apparently never ending list of obscure and not so obscure disk vendors and
products.
5. While I was unable to get confirmation or documentation on file names for
tce repo files, I guessed that localmirrors would be used, but this may be
any random text file in /opt at all, no extensions, I'd have to test to confirm
or deny possible values.
6. To handle more complex debugger failures, added --debug-no-proc,
--debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.
Changes:
1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful
and reliable than I'd first expected when I made the feature, the -xxx was more
an indication of my lack of trust in the method and source, but so far it seems
pretty good, so I bumped it up to an -x option. Note that also, it's quite useful
to know the vendor of, say, your network or graphics card, not just the actual
device internal data, which is all inxi has ever shown previously.
2. Small change, if no partition type data is found, dev, remote, mapped, default
now says 'source:' instead of 'dev:' which makes more sense. Note that df calls
that column 'source', so I decided to go with their language for the default not
found case. Also changed mapped to say mapped. This was part of a bit of a
refactor of the partition type logic, enhanced by adding mapped to existing types,
and moved the entire type detection block into the main data generator, and out
of the data line constructor.
Optimizations:
1. Tested, and dumped, List::Util first() as a possible way to speed up grep
searches of arrays, where the goal is just to see if something is in an array. My
expectation was that first(), returning the first found instance of the search term,
would of course be faster since it will always exit the search loop was met with
the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin.
I tested this fairly carefully, and used NYTProf optimizer tool and the results were
totally consistent, first() was always much slower than grep(), no matter what size
the array is. I assume this means the core C programming that makes grep is simply
much better than the File::Util module programming that makes first(). Removed
first() and now know that nothing will be faster than grep so no need to look there
for speed improvements.
The moral of the story: just because something should in theory be faster, does
sadly not mean it will be faster, for there are bigger things at work, skill of
the programmers who made the logic, how perl handles external vs internal tools,
and so on. As an aside, this forms a fairly consistent pattern where I've found
Perl by itself to be faster than modules in many cases, that is, it's faster to
write the code out than to use a module in many cases that I have tested, so I
will always test such ideas and dump every one that is in fact slower than native
Perl builtins.
2018-10-14 23:16:06 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds version/port(s)/driver version (if available) for each device.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds PCI/USB ID of each device.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
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 21:48:52 +00:00
|
|
|
\- Adds inactive sound servers/APIs, if detected.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New Feature, new version, new man page, new tarball. Laptop users should be happy,
-B option now shows, if available, battery data. Quite good data for systems
with /sys battery data, only rudimentary for systems using dmidecode (BSDs).
dmidecode has no current voltage/charge/current supported capacity.
Main row shows charge and condition. Condition shows you have much capacity the
battery currently has vs its design capacity. Charge shows the Wh/percent of
current capacity of battery (NOT the rated design capacity).
-x adds battery vendor/model info, and battery status (like, charging, discharging,
full).
-xx adds battery serial number and voltage information. Note that voltage information
is presented as Current Voltage / Designed minimum voltage.
-xxx adds battery chemistry (like Li-ion), cycles (note: there's a bug somewhere in
that makes the cycle count always be 0, I don't know if that's in the batteries,
the linux kernel, but it's not inxi, just FYI, the data is simply 0 always in all
my datasets so far.
For dmidecode output, the location of the batter is also shown in -xxx
2016-04-19 00:03:14 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-B\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds vendor/model, battery status (if battery present).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
\- Adds attached battery powered peripherals (\fBDevice\-[number]:\fR) if
|
|
|
|
|
detected (keyboard, mouse, etc.).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds battery \fBvolts:\fR, \fBmin:\fR voltages. Note that if difference is
|
|
|
|
|
critical, that is current voltage is too close to minimum voltage, shows without
|
|
|
|
|
\fB\-x\fR.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-C\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds bogomips to CPU speed report (if available).
|
|
|
|
|
|
|
|
|
|
\- Adds \fBL1:\fR and \fBL3:\fR cache types if either are present/available. For
|
|
|
|
|
BSD or legacy Linux, uses dmidecode + doas/sudo/root. Force use of dmidecode
|
|
|
|
|
cache values by adding \fB\-\-dmidecode\fR. This will override /sys based cache
|
|
|
|
|
data, which tends to be better, so in general don't do that.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds \fBboost: [enabled|disabled]\fR if detected, aka \fBturbo\fR. Not all
|
|
|
|
|
CPUs have this feature.
|
Bug fixes, feature updates, changes!!
Bugs:
1. There was a glitch in the pattern that made -D samsung / seagate not ID right,
fixed.
2. I do not like calling this a bug, because it's not an inxi bug, it's an upstream
regression in the syntax used in /proc/version, they changed a fully predictable
gcc version .... to a random series of embedded/nested parentheses and other random
junk. inxi tries to deal with this regression, which will be perceived as a bug in
systems running kernel 5.8 or newer and inxi 3.1.06 or older, since it will fail to
show the kernel build compiler version since it can't find it in the string.
I really dislike these types of regressions caused by bad ideas done badly and
without any thought to the transmitted knowledge base, but that's how it goes,
no discipline, I miss the graybeards, who cared about things like this.
Fixes:
1. more -D nvme id changes, intel in this case.
2. FreeBSD lsusb changed syntax, which triggered a series of errors when run.
Since I never really got the required data [hint bsd users, do NOT file issues
that you want fixed and then not provide all the data required, otherwise, really,
why did you file the issue? did you expect magic pixies to fly in with the required
data?] See the README.txt for what to do to get issues really handed in BSDs.
tldr; version: if you won't spend the time providing data and access required,
I won't spend the time on the issue, period, since if you don't care enough to
do those simple steps, why on earth do you expect me to?
Changes:
1. -C 'boost' option changed from -xxx feature to -x feature.
Consider it a promotion!
2. Added --dbg 19 switch to enable smart data debugging for -Da.
3. Some new tools to handle impossible data values for some -D situations for SMART
where the smart report contains gibberish values, that was issue #225 -- tools were
convert_hex and is_Hex. The utility for these is limited, but might be of use in
some cases, like handling the above gibberish data value.
2020-09-29 23:22:15 +00:00
|
|
|
|
New version, new man page.
Bugs:
1. Both a fix and a bug, in that inxi had an out of date list of Xorg drivers.
This led to all the newer Intel devices failing to show their drivers in the
Xorg driver lines, like i915, i965, and so on. Updated to full current list of
Xorg drivers. This is not technically a bug since it's simply things that came
into existence after that logic was last updated. But it looks like a bug.
Fixes:
1. Issues #170 and #168 showed a problem with inxi believing it was running in IRC
when Ansible or MOTD started inxi. This is because they are not tty so trip the
non tty flag, which assumes it's in IRC in that case. The fix was to add a
whitelist of known clients based on the parent name inxi discovers while running
inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file
issue reports then not follow them? Who knows.
Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi
which disables the tty test as well. To handle that scenario, that is, when inxi is
not first in the pipe, I added many known terminal client names to the whitelists.
This works in my tests, though the possible terminals, or programs with embedded
terminals, is quite large, but inxi handles most of them automatically. When it
doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
in the meantime.
2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
in some character sets, like greek or russian utf8. The fix was more of a work-around
than a true fix, but inxi now simply checks the weather local time output for wide
characters, and if detected, switches the local date/time format to iso standard,
which is does not contain non ascii characters as far as I can tell. This seemed to
fix the issue.
3. Added iso9660 from excluded file systems for partitions, not sure how inxi
missed that one for so long.
4. See bug 1, expanded and made current supported intel drivers, and a few other
drivers, so now inxi has all the supported xorg drivers again. Updated docs as well
to indicate where to get that data.
Enhancements:
1. As usual, more disk vendor/product ID matches, thanks to linuxlite hardware
database, which never stops providing new or previously unseen disk ids. Latest
favorite? Swissarmy knife maker victorinox Swissflash usb device.
2. Added Elive system base ID.
3. Added Nutyx CARDS repo type.
2019-01-01 05:11:01 +00:00
|
|
|
\- Adds CPU Flags (short list). Use \fB\-f\fR to see full flag/feature list.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds CPU microarchitecture + revision (e.g. Sandy Bridge, K8, ARMv8, P6,
|
|
|
|
|
etc.). Only shows data if detected. Newer microarchitectures will have to be
|
|
|
|
|
added as they appear, and require the CPU family ID, model ID, and stepping.
|
|
|
|
|
|
|
|
|
|
\- Adds, if smt (Simultaneous MultiThreading) is available but disabled, after
|
|
|
|
|
\fBtype:\fR data \fBsmt: disabled\fR. \fBtype: MT\fR means it's enabled. See
|
|
|
|
|
\fB\-Cxxx\fR.
|
2017-07-29 01:42:17 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Examples:
|
|
|
|
|
.br
|
|
|
|
|
\fBarch: Sandy Bridge rev: 2\fR
|
|
|
|
|
.br
|
|
|
|
|
\fBarch: K8 rev.F+ rev: 2\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
If unable to non\-ambiguosly determine architecture, will show something like:
|
|
|
|
|
\fBarch: Amber Lake note: check rev: 9\fR
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds CPU highest speed after \fBavg: [speed] high: [speed]\fR if greater than
|
|
|
|
|
1 core and cores have different speeds. Linux only.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-d\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds more items to \fBFeatures\fR line of optical drive;
|
|
|
|
|
dds rev version to optical drive.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-D\fR
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- Adds drive temperature with disk data.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Method 1: Systems running Linux kernels ~5.6 and newer should have
|
|
|
|
|
\fBdrivetemp\fR module data available. If so, drive temps will come from
|
|
|
|
|
/sys data for each drive, and will not require root or hddtemp. This method
|
|
|
|
|
is MUCH faster than using hddtemp. Note that NVMe drives do not require
|
|
|
|
|
\fBdrivetemp\fR.
|
2014-04-03 18:35:14 +00:00
|
|
|
|
Bug fixes!! Fixes!!! Refactors!!! Edits!!!
Bugs:
1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and
partition scheme would never show, oops.
2. Tiny bug kept one specific smart value from ever showing, typo.
Fixes:
1. Accidentally followed Arch linux derived distro page, which claims KaOS as
arch derived, when of course it's not, it's its own distro, own toolchain, etc.
I kind of knew this but had forgotten, then I believed the Arch derived distro
page, oh well. Resulted in KaOS being listed with arch linux as system base
with -Sx. Arch should fix this, it's not like it's hard, just remove the distro
from the page.
2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends,
man, and help to hopefully make this clear. Debian will be dropping hddtemp,
which is not maintained, sometime in the coming years, sooner than later.
Note that users unfortunately have to manually enable drivetemp module unless
their distros enable it by default, but the man/recommands/help explain that.
3. Fixed smart indentation issues, that went along with code change 1, was
failing to indent one further level for failed/age values like it's supposed
to.
Enhancements:
1. Added /proc/device to debugger, that will help track block device main numbers
2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows
eternally, thanks linux-lite hardware database users!! and other inxi users,
whose outputs sometimes reveal a failure or two.
3. Added loaded kernel module tests to --recommends, this was mostly to let users
know that drivetemp is needed if you want non superuser fast drive temps, and
that this came along with kernels 5.6 or newer. Hopefully word will start drifting
out. Note that if inxi is using drivetemp values, drive temps will appear as
regular user with -Dx, and will be to 1 decimal place. hddtemp temps are
integers, and requires sudo to display the temps.
4. To handle issue #239 which I'd thought of trying off and on, but never did,
added option to -Dxxx to show SSD if a positive SSD ID was made to rotation:
So rotation will show either nothing, if no rotation or ssd data is detected,
the disk speed in rpm, or SSD if an SSD device. There may be corner cases where
this is wrong, but I don't have data for that, for example, if a disk is parked
and has zero rotation but is a HDD, not as SSD. I don't know what the data
looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is
installed, it should be right almost all the time, and with regular -Dxxx, it's
going to be right almost always, with a few corner cases. That slight
uncertainty is why I never implemented this before. Legacy drives also sometimes
did not report rotation speeds even when HDD, so those may create issues,
but inxi will only call it an SSD if it's an nvme, mmcblk device, both are
easy to ID as SSD, or if it meets certain conditions. It will not call a drive
an SSD if it was unable to meet those conditions.
INTERNAL CODE CHANGES:
1. Refactored the output logic for DiskData, that was messy, split it into a few
subs, and also refactored the way smartctl data was loaded and used, that's
much cleaner and easier to use now. Split the previous 1 big sub into:
totals_output(), drives_output(), and smart_output().
Also split out the smart field arrays into a separate sub, which loads
references to avoid creating new arrays and copying them all over when outputting
smart data. References are weird to work with directly but they are MUCH faster
to use, so I'm moving as much of the internal logic to use array raferences
instead of dereferenced arrays/hashes assigned to a new array, or hash.
2. Redid all the output modules and renamed them to be more consistent and
predictable, and redid the logic here and there to make the get() items be fairly
similar on all the data builder packages. Now as with the data subs, which
generally end in _data, now most of the output subs end with _output.
3. Roughly finished the process started in 3.2, got rid of redundant array loads,
changed:
@something = something_data();
push (@rows,@something);
to:
push (@rows,something_data());
which avoids creating an extra array, this also let me remove many arrays overall.
4. Missed a few hashes in machine data that were being passed directly, not as
references, to other subs, corrected that. I think I missed those because they
were %, so the search I did for @ in sub arg lists didn't catch the % hashes.
2021-02-09 01:07:34 +00:00
|
|
|
If your \fBdrivetemp\fR module is not enabled, enable it:
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fixes!! Fixes!!! Refactors!!! Edits!!!
Bugs:
1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and
partition scheme would never show, oops.
2. Tiny bug kept one specific smart value from ever showing, typo.
Fixes:
1. Accidentally followed Arch linux derived distro page, which claims KaOS as
arch derived, when of course it's not, it's its own distro, own toolchain, etc.
I kind of knew this but had forgotten, then I believed the Arch derived distro
page, oh well. Resulted in KaOS being listed with arch linux as system base
with -Sx. Arch should fix this, it's not like it's hard, just remove the distro
from the page.
2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends,
man, and help to hopefully make this clear. Debian will be dropping hddtemp,
which is not maintained, sometime in the coming years, sooner than later.
Note that users unfortunately have to manually enable drivetemp module unless
their distros enable it by default, but the man/recommands/help explain that.
3. Fixed smart indentation issues, that went along with code change 1, was
failing to indent one further level for failed/age values like it's supposed
to.
Enhancements:
1. Added /proc/device to debugger, that will help track block device main numbers
2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows
eternally, thanks linux-lite hardware database users!! and other inxi users,
whose outputs sometimes reveal a failure or two.
3. Added loaded kernel module tests to --recommends, this was mostly to let users
know that drivetemp is needed if you want non superuser fast drive temps, and
that this came along with kernels 5.6 or newer. Hopefully word will start drifting
out. Note that if inxi is using drivetemp values, drive temps will appear as
regular user with -Dx, and will be to 1 decimal place. hddtemp temps are
integers, and requires sudo to display the temps.
4. To handle issue #239 which I'd thought of trying off and on, but never did,
added option to -Dxxx to show SSD if a positive SSD ID was made to rotation:
So rotation will show either nothing, if no rotation or ssd data is detected,
the disk speed in rpm, or SSD if an SSD device. There may be corner cases where
this is wrong, but I don't have data for that, for example, if a disk is parked
and has zero rotation but is a HDD, not as SSD. I don't know what the data
looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is
installed, it should be right almost all the time, and with regular -Dxxx, it's
going to be right almost always, with a few corner cases. That slight
uncertainty is why I never implemented this before. Legacy drives also sometimes
did not report rotation speeds even when HDD, so those may create issues,
but inxi will only call it an SSD if it's an nvme, mmcblk device, both are
easy to ID as SSD, or if it meets certain conditions. It will not call a drive
an SSD if it was unable to meet those conditions.
INTERNAL CODE CHANGES:
1. Refactored the output logic for DiskData, that was messy, split it into a few
subs, and also refactored the way smartctl data was loaded and used, that's
much cleaner and easier to use now. Split the previous 1 big sub into:
totals_output(), drives_output(), and smart_output().
Also split out the smart field arrays into a separate sub, which loads
references to avoid creating new arrays and copying them all over when outputting
smart data. References are weird to work with directly but they are MUCH faster
to use, so I'm moving as much of the internal logic to use array raferences
instead of dereferenced arrays/hashes assigned to a new array, or hash.
2. Redid all the output modules and renamed them to be more consistent and
predictable, and redid the logic here and there to make the get() items be fairly
similar on all the data builder packages. Now as with the data subs, which
generally end in _data, now most of the output subs end with _output.
3. Roughly finished the process started in 3.2, got rid of redundant array loads,
changed:
@something = something_data();
push (@rows,@something);
to:
push (@rows,something_data());
which avoids creating an extra array, this also let me remove many arrays overall.
4. Missed a few hashes in machine data that were being passed directly, not as
references, to other subs, corrected that. I think I missed those because they
were %, so the search I did for @ in sub arg lists didn't catch the % hashes.
2021-02-09 01:07:34 +00:00
|
|
|
\fBmodprobe drivetemp\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Bug fixes!! Fixes!!! Refactors!!! Edits!!!
Bugs:
1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and
partition scheme would never show, oops.
2. Tiny bug kept one specific smart value from ever showing, typo.
Fixes:
1. Accidentally followed Arch linux derived distro page, which claims KaOS as
arch derived, when of course it's not, it's its own distro, own toolchain, etc.
I kind of knew this but had forgotten, then I believed the Arch derived distro
page, oh well. Resulted in KaOS being listed with arch linux as system base
with -Sx. Arch should fix this, it's not like it's hard, just remove the distro
from the page.
2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends,
man, and help to hopefully make this clear. Debian will be dropping hddtemp,
which is not maintained, sometime in the coming years, sooner than later.
Note that users unfortunately have to manually enable drivetemp module unless
their distros enable it by default, but the man/recommands/help explain that.
3. Fixed smart indentation issues, that went along with code change 1, was
failing to indent one further level for failed/age values like it's supposed
to.
Enhancements:
1. Added /proc/device to debugger, that will help track block device main numbers
2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows
eternally, thanks linux-lite hardware database users!! and other inxi users,
whose outputs sometimes reveal a failure or two.
3. Added loaded kernel module tests to --recommends, this was mostly to let users
know that drivetemp is needed if you want non superuser fast drive temps, and
that this came along with kernels 5.6 or newer. Hopefully word will start drifting
out. Note that if inxi is using drivetemp values, drive temps will appear as
regular user with -Dx, and will be to 1 decimal place. hddtemp temps are
integers, and requires sudo to display the temps.
4. To handle issue #239 which I'd thought of trying off and on, but never did,
added option to -Dxxx to show SSD if a positive SSD ID was made to rotation:
So rotation will show either nothing, if no rotation or ssd data is detected,
the disk speed in rpm, or SSD if an SSD device. There may be corner cases where
this is wrong, but I don't have data for that, for example, if a disk is parked
and has zero rotation but is a HDD, not as SSD. I don't know what the data
looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is
installed, it should be right almost all the time, and with regular -Dxxx, it's
going to be right almost always, with a few corner cases. That slight
uncertainty is why I never implemented this before. Legacy drives also sometimes
did not report rotation speeds even when HDD, so those may create issues,
but inxi will only call it an SSD if it's an nvme, mmcblk device, both are
easy to ID as SSD, or if it meets certain conditions. It will not call a drive
an SSD if it was unable to meet those conditions.
INTERNAL CODE CHANGES:
1. Refactored the output logic for DiskData, that was messy, split it into a few
subs, and also refactored the way smartctl data was loaded and used, that's
much cleaner and easier to use now. Split the previous 1 big sub into:
totals_output(), drives_output(), and smart_output().
Also split out the smart field arrays into a separate sub, which loads
references to avoid creating new arrays and copying them all over when outputting
smart data. References are weird to work with directly but they are MUCH faster
to use, so I'm moving as much of the internal logic to use array raferences
instead of dereferenced arrays/hashes assigned to a new array, or hash.
2. Redid all the output modules and renamed them to be more consistent and
predictable, and redid the logic here and there to make the get() items be fairly
similar on all the data builder packages. Now as with the data subs, which
generally end in _data, now most of the output subs end with _output.
3. Roughly finished the process started in 3.2, got rid of redundant array loads,
changed:
@something = something_data();
push (@rows,@something);
to:
push (@rows,something_data());
which avoids creating an extra array, this also let me remove many arrays overall.
4. Missed a few hashes in machine data that were being passed directly, not as
references, to other subs, corrected that. I think I missed those because they
were %, so the search I did for @ in sub arg lists didn't catch the % hashes.
2021-02-09 01:07:34 +00:00
|
|
|
Once enabled, add \fBdrivetemp\fR to \fB/etc/modules\fR or
|
|
|
|
|
\fB/etc/modules\-load.d/***.conf\fR so it starts automatically.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
If you see drive temps running as regular user and you did not configure system
|
|
|
|
|
to use doas/sudo hddtemp, then your system supports this feature. If no /sys
|
|
|
|
|
data is found, inxi will try to use hddtemp methods instead for that drive.
|
|
|
|
|
Hint: if temp is /sys sourced, the temp will be to 1 decimal, like 34.8, if
|
|
|
|
|
hddtemp sourced, they will be integers.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
Bug fixes!! Fixes!!! Refactors!!! Edits!!!
Bugs:
1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and
partition scheme would never show, oops.
2. Tiny bug kept one specific smart value from ever showing, typo.
Fixes:
1. Accidentally followed Arch linux derived distro page, which claims KaOS as
arch derived, when of course it's not, it's its own distro, own toolchain, etc.
I kind of knew this but had forgotten, then I believed the Arch derived distro
page, oh well. Resulted in KaOS being listed with arch linux as system base
with -Sx. Arch should fix this, it's not like it's hard, just remove the distro
from the page.
2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends,
man, and help to hopefully make this clear. Debian will be dropping hddtemp,
which is not maintained, sometime in the coming years, sooner than later.
Note that users unfortunately have to manually enable drivetemp module unless
their distros enable it by default, but the man/recommands/help explain that.
3. Fixed smart indentation issues, that went along with code change 1, was
failing to indent one further level for failed/age values like it's supposed
to.
Enhancements:
1. Added /proc/device to debugger, that will help track block device main numbers
2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows
eternally, thanks linux-lite hardware database users!! and other inxi users,
whose outputs sometimes reveal a failure or two.
3. Added loaded kernel module tests to --recommends, this was mostly to let users
know that drivetemp is needed if you want non superuser fast drive temps, and
that this came along with kernels 5.6 or newer. Hopefully word will start drifting
out. Note that if inxi is using drivetemp values, drive temps will appear as
regular user with -Dx, and will be to 1 decimal place. hddtemp temps are
integers, and requires sudo to display the temps.
4. To handle issue #239 which I'd thought of trying off and on, but never did,
added option to -Dxxx to show SSD if a positive SSD ID was made to rotation:
So rotation will show either nothing, if no rotation or ssd data is detected,
the disk speed in rpm, or SSD if an SSD device. There may be corner cases where
this is wrong, but I don't have data for that, for example, if a disk is parked
and has zero rotation but is a HDD, not as SSD. I don't know what the data
looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is
installed, it should be right almost all the time, and with regular -Dxxx, it's
going to be right almost always, with a few corner cases. That slight
uncertainty is why I never implemented this before. Legacy drives also sometimes
did not report rotation speeds even when HDD, so those may create issues,
but inxi will only call it an SSD if it's an nvme, mmcblk device, both are
easy to ID as SSD, or if it meets certain conditions. It will not call a drive
an SSD if it was unable to meet those conditions.
INTERNAL CODE CHANGES:
1. Refactored the output logic for DiskData, that was messy, split it into a few
subs, and also refactored the way smartctl data was loaded and used, that's
much cleaner and easier to use now. Split the previous 1 big sub into:
totals_output(), drives_output(), and smart_output().
Also split out the smart field arrays into a separate sub, which loads
references to avoid creating new arrays and copying them all over when outputting
smart data. References are weird to work with directly but they are MUCH faster
to use, so I'm moving as much of the internal logic to use array raferences
instead of dereferenced arrays/hashes assigned to a new array, or hash.
2. Redid all the output modules and renamed them to be more consistent and
predictable, and redid the logic here and there to make the get() items be fairly
similar on all the data builder packages. Now as with the data subs, which
generally end in _data, now most of the output subs end with _output.
3. Roughly finished the process started in 3.2, got rid of redundant array loads,
changed:
@something = something_data();
push (@rows,@something);
to:
push (@rows,something_data());
which avoids creating an extra array, this also let me remove many arrays overall.
4. Missed a few hashes in machine data that were being passed directly, not as
references, to other subs, corrected that. I think I missed those because they
were %, so the search I did for @ in sub arg lists didn't catch the % hashes.
2021-02-09 01:07:34 +00:00
|
|
|
Method 2: if you have hddtemp installed, if you are root
|
|
|
|
|
or if you have added to \fB/etc/sudoers\fR (sudo v. 1.7 or newer):
|
|
|
|
|
|
|
|
|
|
.B <username> ALL = NOPASSWD: /usr/sbin/hddtemp (sample)
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
doas users: see \fBman doas.conf\fR for setup.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
You can force use of \fBhddtemp\fR for all drives using \fB\-\-hddtemp\fR.
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- If free LVM volume group size detected (root required), show \fBlvm\-free:\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
on Local Storage line. This is how much unused space the VGs contain, that is,
|
|
|
|
|
space not assigned to LVs.
|
|
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-E\fR (\fB\-\-bluetooth\fR)
|
|
|
|
|
\- Adds (if available and/or relevant) \fBvendor:\fR item, which shows
|
|
|
|
|
specific vendor [product] information.
|
|
|
|
|
|
|
|
|
|
\- Adds PCI/USB Bus ID of each device.
|
|
|
|
|
|
|
|
|
|
\- Adds driver version (if available) for each device.
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- 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.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-G\fR
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
\- Adds GPU micro\-architecture (if AMD/Intel/Nvidia and detected).
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCI/USB ID of each device.
|
|
|
|
|
|
New version, new man. Fixes, stitches, and returns!!
Bugs:
1. As a fix (3), failure to handle spaces in mount source names. More of a fix than
a bug, since it was an old issue #63.
2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data
tripping null data or unreadable file errors, but I'll call those bugs since they
look like bugs to end users. See Fixes for more.
3. See Fix 4, this is sort of a bug, inxi failed to return expected values on
success/failure.
Fixes:
1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented
internally. This is now corrected.
2. Apple OSX was returning errors, those were fixed.
3. Finally handled ancient issue #63, support now there for spaces in remote source
name. This means that both spaces in source block name, and mount point name, are
in theory both handled now. This was also to fix an osx issue #164 despite the
fact that technically I do not support osx beyond fixing errors, but since in this
case the issue was a long standing one, I fixed it for everything.
4. Big fix, I'd completely left undone proper unix type error number returns in
inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi
returns integer success/error numbers as expected.
5. OSX xml based version info broke, of course, naturally it would, so I added in
an osx fallback where if no distro version detected, use fallback unix method, which
is what all the other unices use.
6. Along with space in source name, fixed mapped handling a bit more too for
partitions.
6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure
how I'd missed those for so long.
7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a,
sigh, human readable default format, in M, so to handle this for all bsds, I had
to make a dynamic column detection for avm and fre, and use those after, and also
i had to add in a M detection, if found, *1024 and strip out M, sigh.
8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks
does not always use the same order in comma separated list, saw user case where
the first item after : was the MB size, not the second. Made detection dynamic.
9. Due to Android case, found types where no cpu speed data was found, no max speed
at least, which tripped an error due to null data for ARM, this is now handled,
now cpu speed min/max read permissions in /sys are checked first before trying to
read, and default failures are better handled.
10. On man page, added in clarification of the moving of Memory: item from Info:
line to ram Memory: line, explaining when it appears where. I do not removing the
item from -I, I may revert that change, I find it non-intuitive to move that
around.
Enhancements:
1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this
closes issues #166 #165 #162
2. Improved documentation a bit to avoid ambiguity re how to get colors in output.
That handles issue #161, thanks fugo for the nudge to improve the documentation.
3. First inxi on Android tests, using termux, which has a debian based apt
type installer, got inxi running on at least two devices, including pixel2, but
discovered that apparently as of android 5, /sys is now locked up in terms of
wildcard reads, but further analysis is required, but as of now, inxi works in
termux, but fails to get any Device data for A, G, or N. Thus it also fails to match
IF to Device, so none of the IP data shows up. The latter will probably be fixed
since Android has ip and ifconfig already, or termux does, but so far I found no
way to get device data for ARM in Android 5.x and greater (checked on
android 7 and 9 in real phones).
4. More disk vendors!! thanks linuxlite / linux hardware database for offering an
apparently never ending list of obscure and not so obscure disk vendors and
products.
5. While I was unable to get confirmation or documentation on file names for
tce repo files, I guessed that localmirrors would be used, but this may be
any random text file in /opt at all, no extensions, I'd have to test to confirm
or deny possible values.
6. To handle more complex debugger failures, added --debug-no-proc,
--debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.
Changes:
1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful
and reliable than I'd first expected when I made the feature, the -xxx was more
an indication of my lack of trust in the method and source, but so far it seems
pretty good, so I bumped it up to an -x option. Note that also, it's quite useful
to know the vendor of, say, your network or graphics card, not just the actual
device internal data, which is all inxi has ever shown previously.
2. Small change, if no partition type data is found, dev, remote, mapped, default
now says 'source:' instead of 'dev:' which makes more sense. Note that df calls
that column 'source', so I decided to go with their language for the default not
found case. Also changed mapped to say mapped. This was part of a bit of a
refactor of the partition type logic, enhanced by adding mapped to existing types,
and moved the entire type detection block into the main data generator, and out
of the data line constructor.
Optimizations:
1. Tested, and dumped, List::Util first() as a possible way to speed up grep
searches of arrays, where the goal is just to see if something is in an array. My
expectation was that first(), returning the first found instance of the search term,
would of course be faster since it will always exit the search loop was met with
the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin.
I tested this fairly carefully, and used NYTProf optimizer tool and the results were
totally consistent, first() was always much slower than grep(), no matter what size
the array is. I assume this means the core C programming that makes grep is simply
much better than the File::Util module programming that makes first(). Removed
first() and now know that nothing will be faster than grep so no need to look there
for speed improvements.
The moral of the story: just because something should in theory be faster, does
sadly not mean it will be faster, for there are bigger things at work, skill of
the programmers who made the logic, how perl handles external vs internal tools,
and so on. As an aside, this forms a fairly consistent pattern where I've found
Perl by itself to be faster than modules in many cases, that is, it's faster to
write the code out than to use a module in many cases that I have tested, so I
will always test such ideas and dump every one that is in fact slower than native
Perl builtins.
2018-10-14 23:16:06 +00:00
|
|
|
\- Adds (if available and/or relevant) \fBvendor:\fR item, which shows
|
|
|
|
|
specific vendor [product] information.
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- \fBX.org:\fR Adds direct rendering status.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- \fBX.org:\fR Adds (for single GPU, nvidia driver) screen number that GPU is
|
|
|
|
|
running on.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- Adds device temperature for each discrete device (Linux only).
|
|
|
|
|
|
2012-10-19 19:43:26 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-i\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds IP v6 additional scope data, like Global, Site, Temporary for
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
each interface.
|
2017-05-31 22:41:17 +00:00
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
Note that there is no way we are aware of to filter out the deprecated
|
2018-04-06 22:52:08 +00:00
|
|
|
IP v6 scope site/global temporary addresses from the output of
|
2018-04-04 06:41:06 +00:00
|
|
|
\fBifconfig\fR. The \fBip\fR tool shows that clearly.
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBip\-v6\-temporary\fR \- (\fBip\fR tool only), scope global temporary.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
Scope global temporary deprecated is not shown
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBip\-v6\-global\fR \- scope global (\fBifconfig\fR will show this for
|
|
|
|
|
all types, global, global temporary, and global temporary deprecated,
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
\fBip\fR shows it only for global)
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBip\-v6\-link\fR \- scope link (\fBip\fR/\fBifconfig\fR) \- default
|
|
|
|
|
for \fB\-i\fR.
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBip\-v6\-site\fR \- scope site (\fBip\fR/\fBifconfig\fR). This has been
|
|
|
|
|
deprecated in IPv6, but still exists. \fBifconfig\fR may show multiple site
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
values, as with global temporary, and global temporary deprecated.
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2017-06-09 17:14:28 +00:00
|
|
|
\fBip\-v6\-unknown\fR \- unknown scope
|
2017-05-31 22:41:17 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-I\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds current init system (and init rc in some cases, like OpenRC).
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
With \fB\-xx\fR, shows init/rc version number, if available.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds default system gcc. With \fB\-xx\fR, also show other installed gcc
|
2018-04-06 22:52:08 +00:00
|
|
|
versions.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
\- Adds current runlevel/target (not available with all init systems).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
\- Adds total packages discovered in system. See \fB\-xx\fR and \fB\-a\fR
|
|
|
|
|
for per package manager types output. Moves to \fBRepos\fR if \fB\-rx\fR.
|
|
|
|
|
|
|
|
|
|
If your package manager is not supported, please file an issue and we'll add it.
|
|
|
|
|
That requires the full output of the query or method to discover all installed
|
|
|
|
|
packages on your system, as well of course as the command or method used to
|
|
|
|
|
discover those.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- If in shell (i.e. not in IRC client), adds shell version number, if
|
|
|
|
|
available.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
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 18:59:56 +00:00
|
|
|
.B \-x \-j\fR (\fB\-\-swap\fR)
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
Add \fBmapper:\fR. See \fB\-x \-o\fR.
|
|
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-J\fR (\fB\-\-usb\fR)
|
|
|
|
|
\- For Devices, adds driver(s).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- 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.
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
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 18:59:56 +00:00
|
|
|
.B \-x \-L\fR (\fB\-\-logical\fR)
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds \fBdm: dm-x\fR to VG > LV and other Device types. This can help
|
|
|
|
|
tracking down which device belongs to what.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
.B \-x \-m\fR, \fB\-\-memory\-modules\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- If present, adds maximum memory module/device size in the Array line.
|
2018-04-06 22:52:08 +00:00
|
|
|
Only some systems will have this data available. Shows estimate if it can
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
generate one.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-N\fR
|
New version, new man. Fixes, stitches, and returns!!
Bugs:
1. As a fix (3), failure to handle spaces in mount source names. More of a fix than
a bug, since it was an old issue #63.
2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data
tripping null data or unreadable file errors, but I'll call those bugs since they
look like bugs to end users. See Fixes for more.
3. See Fix 4, this is sort of a bug, inxi failed to return expected values on
success/failure.
Fixes:
1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented
internally. This is now corrected.
2. Apple OSX was returning errors, those were fixed.
3. Finally handled ancient issue #63, support now there for spaces in remote source
name. This means that both spaces in source block name, and mount point name, are
in theory both handled now. This was also to fix an osx issue #164 despite the
fact that technically I do not support osx beyond fixing errors, but since in this
case the issue was a long standing one, I fixed it for everything.
4. Big fix, I'd completely left undone proper unix type error number returns in
inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi
returns integer success/error numbers as expected.
5. OSX xml based version info broke, of course, naturally it would, so I added in
an osx fallback where if no distro version detected, use fallback unix method, which
is what all the other unices use.
6. Along with space in source name, fixed mapped handling a bit more too for
partitions.
6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure
how I'd missed those for so long.
7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a,
sigh, human readable default format, in M, so to handle this for all bsds, I had
to make a dynamic column detection for avm and fre, and use those after, and also
i had to add in a M detection, if found, *1024 and strip out M, sigh.
8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks
does not always use the same order in comma separated list, saw user case where
the first item after : was the MB size, not the second. Made detection dynamic.
9. Due to Android case, found types where no cpu speed data was found, no max speed
at least, which tripped an error due to null data for ARM, this is now handled,
now cpu speed min/max read permissions in /sys are checked first before trying to
read, and default failures are better handled.
10. On man page, added in clarification of the moving of Memory: item from Info:
line to ram Memory: line, explaining when it appears where. I do not removing the
item from -I, I may revert that change, I find it non-intuitive to move that
around.
Enhancements:
1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this
closes issues #166 #165 #162
2. Improved documentation a bit to avoid ambiguity re how to get colors in output.
That handles issue #161, thanks fugo for the nudge to improve the documentation.
3. First inxi on Android tests, using termux, which has a debian based apt
type installer, got inxi running on at least two devices, including pixel2, but
discovered that apparently as of android 5, /sys is now locked up in terms of
wildcard reads, but further analysis is required, but as of now, inxi works in
termux, but fails to get any Device data for A, G, or N. Thus it also fails to match
IF to Device, so none of the IP data shows up. The latter will probably be fixed
since Android has ip and ifconfig already, or termux does, but so far I found no
way to get device data for ARM in Android 5.x and greater (checked on
android 7 and 9 in real phones).
4. More disk vendors!! thanks linuxlite / linux hardware database for offering an
apparently never ending list of obscure and not so obscure disk vendors and
products.
5. While I was unable to get confirmation or documentation on file names for
tce repo files, I guessed that localmirrors would be used, but this may be
any random text file in /opt at all, no extensions, I'd have to test to confirm
or deny possible values.
6. To handle more complex debugger failures, added --debug-no-proc,
--debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.
Changes:
1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful
and reliable than I'd first expected when I made the feature, the -xxx was more
an indication of my lack of trust in the method and source, but so far it seems
pretty good, so I bumped it up to an -x option. Note that also, it's quite useful
to know the vendor of, say, your network or graphics card, not just the actual
device internal data, which is all inxi has ever shown previously.
2. Small change, if no partition type data is found, dev, remote, mapped, default
now says 'source:' instead of 'dev:' which makes more sense. Note that df calls
that column 'source', so I decided to go with their language for the default not
found case. Also changed mapped to say mapped. This was part of a bit of a
refactor of the partition type logic, enhanced by adding mapped to existing types,
and moved the entire type detection block into the main data generator, and out
of the data line constructor.
Optimizations:
1. Tested, and dumped, List::Util first() as a possible way to speed up grep
searches of arrays, where the goal is just to see if something is in an array. My
expectation was that first(), returning the first found instance of the search term,
would of course be faster since it will always exit the search loop was met with
the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin.
I tested this fairly carefully, and used NYTProf optimizer tool and the results were
totally consistent, first() was always much slower than grep(), no matter what size
the array is. I assume this means the core C programming that makes grep is simply
much better than the File::Util module programming that makes first(). Removed
first() and now know that nothing will be faster than grep so no need to look there
for speed improvements.
The moral of the story: just because something should in theory be faster, does
sadly not mean it will be faster, for there are bigger things at work, skill of
the programmers who made the logic, how perl handles external vs internal tools,
and so on. As an aside, this forms a fairly consistent pattern where I've found
Perl by itself to be faster than modules in many cases, that is, it's faster to
write the code out than to use a module in many cases that I have tested, so I
will always test such ideas and dump every one that is in fact slower than native
Perl builtins.
2018-10-14 23:16:06 +00:00
|
|
|
\- Adds (if available and/or relevant) \fBvendor:\fR item, which shows
|
|
|
|
|
specific vendor [product] information.
|
|
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds version/port(s)/driver version (if available) for each device;
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds PCI/USB ID of each device.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- Adds device temperature for each discrete device (Linux only).
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-o\fR, \fB\-x \-p\fR, \fB\-x \-P\fR
|
2021-08-25 03:39:33 +00:00
|
|
|
\- Adds \fBmapper:\fR (the \fB/dev/mapper/\fR partition ID)
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
if mapped partition.
|
|
|
|
|
|
New version, man page, bug fixes, changes, adjustments and cleanups!!!
Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations.
Bugs:
1. In certain corner cases, it appears that lsusb has blank lines, which tripped
errors in inxi output when the usb parser was trying to access split keys that did
not exist. Added in check to make sure split actually resulted in expected data.
2. A red face bug, I'd left the output debugger switched on with json output, so
it was printing out the json data structure with Dumper, that's now switched off.
Hope this doesn't mess anyone up, but it would have mattered only if the person
was using:
--output json --output-type print
It did not effect xml output.
Fixes:
1. Got rid of extra level of -L data structure and output handler. Not visible
to users, but still irksome, so nice to get that fixed. Recursive structures are
confusing, lol, but this extra level was pointless, but to fix it required redoing
the logic a bit for both data generator and output feature.
2. Added in support for --display :0.0, previously it did not support the
.0 addition, but why not, if it works for people, good, if not, makes no difference.
3. There were some missing cases for LVM missing data messages, so the following
fixes were added:
* In cases where lsblk is installed and user is non root, or lvs is not installed,
but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.'
instead of the permissions or missing program error that showed before.
If lsblk is not installed, and lvm is installed (or missing), with lvs not root
readable, the permissiosn message (or missing program) will show since at that
point, inxi has no way to know if there is lvm data or not.
* Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm
has made lvs and vgs fail to return error number on non root start, which is
a bug (pvs does return expected error return). Rather than wait for this bug
to be fixed, inxi will just test if lvs and lsblk lvm data, it will show
permissions message, otherwse the no lvm data message as expected.
I think these cover the last unhandled LVM cases I came across, so ideally, the
lvm data messages will be reasonably correct.
4. Some man page lintian fixes.
5. Changed usb data parser to use 'unless' instead of 'if' in tests since
it's easier to read unless positive tests are true than if negative or
negative etc.
Enhancements:
1. Since I see too often things like -F --no-host -z which is redundant, the
help and man now make it more clear that -z implies --no-host.
2. Even though it's not that pointful, I added in derived Arch Linux system
base like Ubuntu/Debian have. It's not that meaningful because unlike
Ubuntu/Debian, where you want to know what version the derived distro is
based on, Arch is rolling thus no versions, but I figured, why not, it's
easy to do, so might as well make the system base feature a bit more complete.
Note that the way I did this requires that the distro is ID'ed as its derived
distro nanme, not Arch Linux, that will vary depending on how they did their
os-release etc, or distro files, but that's not really an inxi issue, that's
up to them. From what I've been seeing, it looks like more of the derived
distros are being ID'ed in inxi as the derived name, so those should all work
fine. Note that seeing 'base:' requires -Sx.
3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff,
and refactored slightly the backend tools I use, so it's now a bit easier
to handle the data. Thanks linux-lite hardware database, as always, for
having users that really seemt to use every disk variant known to humanity.
Changes:
1. In -G, made FAILED: lower case, and also moved it to be after unloaded:
It was too easy to think that the loaded driver had failed. Also to make it
more explicit, made output like this, in other words, driver: is a container
for the possible children: loaded: unloaded: failed: alternate: which should be
easier to parse and read without mixing up what belongs to what.
driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv
driver: loaded: amdgpu unloaded: vesa failed: ati
Note that if there is no unloaded: driver, failed: would still appear to come after
loaded:, but hopefully it's more clear now.
Basically what we found was that the presence of the uppercase FAILED: drew
the eye so much that it was sometimes not noted that it was a key: following
the driver: item, which itself because it did not list explicitly loaded:
was not as clear as it could have been. By making failed: the same as the
other key names visually, hopefully it will be less easy to think that the
loaded: driver failed:
In a sense, this is a legacy issue, because the original use of FAILED: was for
non free video drivers, to see when xorg had failed to load them, but over
more recent years, the most frequent thing I have been seeing is odd things
like failed: ati, when xorg tries to load the legacy ati driver when amdgpu
is being used.
2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it
more consistent with the other types.
3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced
that with 'device(s)', which is the more accurate term, since the days when these
things were only addon cards are long behind us. I had not noticed that, but it
caught me eye and I realized it was a very deprecated and obsolete syntax, which
did not match the way inxi describes devices today.
4. It was pointed out how incoherent the naming of the item for setting wrap width,
--indent-min and config item INDENT_MIN were super confusing, since it was neither
indent or minimum, it was in fact wrap maximum, so the new options and config items
are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but
it was almost impossible in words to explain this option because the option text
was almost the exact opposite of what the option actually does. Redid the man
and help explanations to make the function of this option/config item more clear.
5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output,
before Hub: was not numbered, but it struck me, it should be, like all the other
auto-incremented counter line starters, like ID-xx:, Device-x:, and so on.
6. Reorganized the main help menu to hopefully be more logical, now it shows the
primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx,
separated by white space per type to make it easier to read. This also moved
the stuff that had been under the -x items back to where they should be, together
with the main output control options. For readability and usability, I think this
will help, the help menu is really long, so the more visual cues it has to make it
clear what each section is, the better I think. Previously -a was the first items,
then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.
2021-01-11 03:20:21 +00:00
|
|
|
Example: \fBID\-4: /home ... dev: /dev/dm-6 mapped: ar0-home\fR
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-r\fR
|
|
|
|
|
\- Adds Package info. See \fB\-Ix\fR
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-R\fR
|
New version, new man. Fine tunings.
New features:
1. for a very few systems that have wmctrl installed, will shows -xxx wm if present
Enhancements:
1. made xorg display server and protocols show more consistently with other layout:
Display: x11 server: X.org 1.9.12 drivers: loaded: ...
if no display protocol found:
Display: server: X.org 1.9.12 drivers: loaded: ...
This brings the -G in line with the other lines, of not putting different data types
inside of parentheses as much as possible. -I still has two of these, but so far it's
not clear how to otherwise show SSH or su/sudo/login in their respective spaces.
Debugger data collector also has something I should have added ages ago, gz filename
now includes the basic 2 digit inxi version number, like 3.0 at end, so I can readily
determine the debugger inxi version, and thus avoid having to root through lots of
versions to find new stuff.
These are all largely cosmetic improvements, or debugger adjustments, except for -Sxxx
now offering wm: if present.
Also changed Desktop: name... (toolkit data) to: Desktop: name... tk: toolkit data
to be more consistent, while not adding great length to the output.
These two changes should also help export to json/xml since that puts unique key/values
back into key value pairs, not merging two together.
2018-04-12 20:23:46 +00:00
|
|
|
\- md\-raid: Adds second RAID Info line with extra data: blocks, chunk size,
|
2018-04-06 22:52:08 +00:00
|
|
|
bitmap (if present). Resync line, shows blocks synced/total blocks.
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Hardware RAID: Adds driver version, Bus ID.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new tarball, new man page. Unless disabled by distribution maintainers, offers
weather -w option. With -x, -xx-, -xxx, shows more information. Basic line is just weather
and system time there. -x adds time zone, which is useful for servers, particurly web servers.
-x also adds wind speed. -xx adds humidity and barometric pressure. -xxx adds a possible new line,
if data is available, heat index, wind chill, and dew point.
-xxx also adds a line for location (blocked by irc/-z) / weather observation time.
-z filter applies as usual to location data, removes it in irc by default. -Z overrides override.
The api this uses is probably going to be dropped at some point, so this is just going to work
while it works, then it will need to be updated at some point, so don't get very attached to it.
Also adds option to, with -w: -! location=<location string>
This lets users send an alternate location using either <city,state> or <postal code>
or <latitude,longitude> (commas for city,state and latitude,longitude are not optional, and the order
must be as listed.
If There is a developer flag if distro maintainers do not want this enabled, simply set:
B_ALLOW_WEATHER='false'
before packaging and the weather feature will be disabled.
2013-05-18 02:04:29 +00:00
|
|
|
.TP
|
New version, new tarball. New features, bug fixes.
This is a big one.
NEW FEATURES:
1. By Request: Disk vendor is now generally going to be shown. Since this uses
empirical data to grab the vendor name, from the model string, it will not always
find anything. When it fails to find vendor data, no vendor: item will show.
Note that some MMC devices will probably not show vendor data, but that's due to
there being no data that reveals that.
2. Extended -sx volts to also show voltage from lm-sensors if present. Many
systems show no voltage data with lm-sensors, but now if any is found, it
will show, same as impi.
3. Moved to lsblk as primary source for partition/unmounted filesystem, uuid, and
label data.
Falls back to previous methods if lsblk does not return data. Some lsblk do not
show complete data unless super user as well.
4. Refactored code to be more logical and clear.
5. Added for OpenBSD -r: /etc/installurl file.
BUG FIXES:
1. CRITICAL: /sys/block/xxx/device/model is in some cases truncating the disk
model name to 16 characters. This is not an inxi bug, it's a bug with /sys itself.
To fix this, inxi now uses for GNU/Linux /dev/disk/by-id data which does not
ever do this truncation. It's also faster I believe to read that directory
once, filter the results, then use the data for vendor/model/serial.
this was also part of the disk vendor data feature.
2. Openbsd networking fix. Was not showing IF data, now it does.
3. Fixed bug with unmounted where sometimes md0 type partitions would show
even though they are in a raid array.
4. Fixed disk rev, now it searches for 3 different files in /sys to get that data.
5. Fixed bug with very old systems, with sudo 1.6 or older, for some reason that
error did not get redirected to /dev/null, so now only using sudo -n after explicit
version test, only if 1.7 or newer.
6. Fixed a few null results in fringe cases for graphics. Resolution now shows
NA for Hz if no hz data found. This was only present on a fringe user case
which is unlikely to ever impact normal X installations.
7. Fixed BSD L2 cache, was showing MiB instead of KiB, wrong math.
2018-05-07 03:43:34 +00:00
|
|
|
.B \-x \-s\fR
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- Adds basic voltages: 12v, 5v, 3.3v, vbat (\fBipmi\fR, \fBlm\-sensors /
|
|
|
|
|
/sys/class/hwmon\fR if present).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new man. Small new enhancements.
1. Added to -s for ipmi, with -x: voltage 12v,5v,3.3v,vbat; for -xx, dimm/soc p1/p2
voltages
2. enhanced wm: feature, needed more filters and protection against redundant data
3. basic apple osx fixes to keep it from crashing, but I'm not spending any more
time on apple junk unless someone pays me for my time, I can't stand the product or
company, it's the total antitheses of freedom or free software, or even openness.
4. openbsd/bsd fixes: openbsd was failing to get cpu flags due to a small oversight
5. -C now shows bits: for the true bits of cpu, not the kernel bits. This is not
a reliable measurement but should be right about 95+ percent of the time, and
basically all of the time for GNU/Linux on Intel/AMD, most of the time for ARM.
When it doesn't know it does not guess, and shows N/A.
6. bsd fix for usb, was running numeric action on string value
7. fixed stderr tool for program_version, now it's hard-coded in program_values
which removes an unneded regex search for every program version test.
8. Mate detection, switched to using mate-sesssion instead of mate-about, the
latter is not getting updated and has the wrong version number on it.
2018-04-17 20:28:16 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-x \-S\fR
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
\- Adds Kernel gcc version.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds to \fBDistro:\fR \fBbase:\fR if detected. System base will only be
|
|
|
|
|
seen on a subset of distributions. The distro must be both derived from a
|
|
|
|
|
parent distro (e.g. Mint from Ubuntu), and explicitly added to the supported
|
|
|
|
|
distributions for this feature. Due to the complexity of distribution
|
|
|
|
|
identification, these will only be added as relatively solid methods are
|
|
|
|
|
found for each distribution system base detection.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, man. Continuing development of EDID and monitor features, bug
fixes, normal fixes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Failed to handle case for monitor positions of array type: 2-2, 3-1, 1-3,
4-4. I'm not sure what structure those are really arranged in, but might be
worth adding in the x+y pos values along with the row-col values.
2. For Monitors and graphics Device ports, if using non free nvidia driver and:
nvidia-drm.modeset=1 not set in grub kernel boot parameters, there will be no
/sys/class/drm data for the nvidia device, and thus no ports data, and no
monitor data.
3. A class of high count DP or DVI port IDs are changed by Xorg drivers to for
example: DP-6 > DP-2-3. This is very difficult to handle and will in general
probably fail unfortunately because that level of port ID abstraction is just
reazlly hard to deal with dynamically.
4. A to-do item: add bus ID children on --slots. This will probablby be in next
inxi.
--------------------------------------------------------------------------------
BUGS:
1. None outside of the various fixes.
--------------------------------------------------------------------------------
FIXES:
1. In sensors, failed to pull out BAT sensor data. In most cases, this would not
lead to any issues, but it could have.
2. This one just slipped my mind, I'd meant to do it, but in Montitor-x:, the
primary ID should have been the 'real' kernel ID, not the mapped: ID, which is
the X.org ID when different from the kernel ID. So mapped should be the Xorg
version when they are different from the kernel version.
3. In Graphics, monitors can show > 1 ratio, failed to set all to :, resulting
in: ratio: 3:2 or 16/10 modes:. Also fixed ParseEDID to output an array of
ratios, which can then be processed as wanted.
4. Monitor map fixes:
* Handle case in monitors where display ID: eDP and sys ID: eDP-1, this only
works if 1 monitor in array. There's a variety of this type of failure, when
X.org or its drivers decide to call the port ID XYZ with no number at all. All
those possible cases are now handled, like eDP > eDP-1, VGA > VGA-1, and so on.
* Added fallback, if no match, and if only 1 monitor, just map them to eachother
if other mappings failed. Prompted by things like: s: DP-6 > d: DP-2-3;
s: eDP-1 > d: DP-4, which are just impossible to create logic to map.
5. Removed 'ati' driver from xorg drivers list, it's simply a wrapper for r128,
mach64, or radeon (and maybe amdgpu), and shows as failed, unloaded, or loaded,
because of this. ati basically assigns the correct driver, that is, but is not
itself a driver. Thanks mrmazda for spotting this issue.
6. Typo on QDI => Quantum Data.
7. Added fallback for monitor model, now using vendor code plus product code
if nothing found for vendor nice name or model. This will show as 'model-id:'
instead of model: to help differentiate the two.
8. Added Monitor product_code to manufacturer if no model name is found.
9. get_pci_vendor was trimming at ' / ' if the product string also contained
' / '. Fix is to ignore 1 character 'words' in the logic.
10. In Slots, failed to remove_duplicates in the slot info field, leading to
redundant output strings. See Enhancement 3 and Code 4.
11. See Change 3, finally made -S section use full key: value pair, which makes
stuff more explicit, like:
System:
Host: yawn
Kernel: 5.16.0-11.1-liquorix-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 11.2.0
Desktop: Xfce
v: 4.16.0
tk: Gtk
v: 3.24.24
info: xfce4-panel
wm: xfwm
v: 4.16.1
vt: 7
dm:
1: LightDM
v: 1.26.0
2: SDDM
note: stopped
Distro: Debian GNU/Linux bookworm/sid
12. Fix for mageia and lsb distro data, force use of os-release for mageia if
detected. That overrides the forced use of lsb release for mandrake/mandriva,
because for some reason mageia has decided to carry ALL the legacy distro files:
'/etc/lsb-release',
'/etc/lsb-release.d',
'/etc/mageia-release',
'/etc/mandrake-release',
'/etc/mandrakelinux-release',
'/etc/mandriva-release',
'/etc/os-release',
'/etc/redhat-release',
'/etc/system-release'
which is really not what this stuff is intended for, if it's an actual derived
distro from a living base, then yes, include the base file, but all these have
the same distro id data for mageia, none for the derived distros.
Also, fixed an lsb release thing to avoid using codename if codename contains
release number as well. Since lsb_release is totally legacy at this point, who
cares if we might miss a specific codename here and there on legacy system.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added Color Characteristics to EDID parser, for some reason that had been
left out.
2. Added advanced EDID output option --edid, that allows for showing more
advanced EDID data than is appropriate for most users cases. Ihcludes errors,
color characteristics chroma: (chromacity), full modes, not just min/max.
3. In --slots, added bus-ID.
Also extended report quality, made more granular, got rid of single blob from
Type and Designation and now get more accurate and useful data.
4. In cases with > 1 DM, check to see if one or more are stopped or disabled, =
and add (stopped) if it was detected in running service as stopped.
--------------------------------------------------------------------------------
CHANGES:
1. Reversed monitor ID and mapped: ID values, that was a mistake, the mapped:
item was supposed to contain the X.org mapped name, and the primary ID was
supposed to be the actual real ID the kernel uses. Not a huge deal either way,
but there it is.
2. Include disabled but connected Monitors. This works around nvidia bug showing
monitors disabled when they are enabled, but also allows for showing connected
monitors, though without as much data.
3. Made the last holdout -S > -Sa use strict full key: value pair output, like
Desktop: XFCE v: 4.14.12 and so on.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added help/man for --edid info.
--------------------------------------------------------------------------------
CODE:
1. In ParseEDID: made new key: edid_error, which contains an array ref of 1 or
more edid errors. The previous version did a poor job and returned only the
first error found, so there could have been > 1 error, and you'd never know it.
This changes check_parsed_edid to _check_parsed_edid(). and adds a utility tool
_edid_error, which grabs the message from main::message, giving better output
integration.
This also allows for future error handling expansion quite easily.
2. In map_monitor_ids() fixed matching pattern, made more robust and explicit,
to catch things like s: eDP-1 d: eDP or eDP-1-1, both have been seen. Also added
fallback for single monitor, just map them to eachother if mapping failed.
3. get_pci_vendor() added test for using anything that is 1 character length,
to not break on 1 character length string matches.
4. Fully refactored --slots, that was originally written purely as a proof of
concept in terms of adding a new feature during the original inxi 2.9 rewrite,
and was never actually touched after that.
2022-03-24 18:45:05 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-x \-\-slots\fR
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\- Adds slot \fBbus\-ID:\fR, if found.
|
New version, man. Continuing development of EDID and monitor features, bug
fixes, normal fixes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Failed to handle case for monitor positions of array type: 2-2, 3-1, 1-3,
4-4. I'm not sure what structure those are really arranged in, but might be
worth adding in the x+y pos values along with the row-col values.
2. For Monitors and graphics Device ports, if using non free nvidia driver and:
nvidia-drm.modeset=1 not set in grub kernel boot parameters, there will be no
/sys/class/drm data for the nvidia device, and thus no ports data, and no
monitor data.
3. A class of high count DP or DVI port IDs are changed by Xorg drivers to for
example: DP-6 > DP-2-3. This is very difficult to handle and will in general
probably fail unfortunately because that level of port ID abstraction is just
reazlly hard to deal with dynamically.
4. A to-do item: add bus ID children on --slots. This will probablby be in next
inxi.
--------------------------------------------------------------------------------
BUGS:
1. None outside of the various fixes.
--------------------------------------------------------------------------------
FIXES:
1. In sensors, failed to pull out BAT sensor data. In most cases, this would not
lead to any issues, but it could have.
2. This one just slipped my mind, I'd meant to do it, but in Montitor-x:, the
primary ID should have been the 'real' kernel ID, not the mapped: ID, which is
the X.org ID when different from the kernel ID. So mapped should be the Xorg
version when they are different from the kernel version.
3. In Graphics, monitors can show > 1 ratio, failed to set all to :, resulting
in: ratio: 3:2 or 16/10 modes:. Also fixed ParseEDID to output an array of
ratios, which can then be processed as wanted.
4. Monitor map fixes:
* Handle case in monitors where display ID: eDP and sys ID: eDP-1, this only
works if 1 monitor in array. There's a variety of this type of failure, when
X.org or its drivers decide to call the port ID XYZ with no number at all. All
those possible cases are now handled, like eDP > eDP-1, VGA > VGA-1, and so on.
* Added fallback, if no match, and if only 1 monitor, just map them to eachother
if other mappings failed. Prompted by things like: s: DP-6 > d: DP-2-3;
s: eDP-1 > d: DP-4, which are just impossible to create logic to map.
5. Removed 'ati' driver from xorg drivers list, it's simply a wrapper for r128,
mach64, or radeon (and maybe amdgpu), and shows as failed, unloaded, or loaded,
because of this. ati basically assigns the correct driver, that is, but is not
itself a driver. Thanks mrmazda for spotting this issue.
6. Typo on QDI => Quantum Data.
7. Added fallback for monitor model, now using vendor code plus product code
if nothing found for vendor nice name or model. This will show as 'model-id:'
instead of model: to help differentiate the two.
8. Added Monitor product_code to manufacturer if no model name is found.
9. get_pci_vendor was trimming at ' / ' if the product string also contained
' / '. Fix is to ignore 1 character 'words' in the logic.
10. In Slots, failed to remove_duplicates in the slot info field, leading to
redundant output strings. See Enhancement 3 and Code 4.
11. See Change 3, finally made -S section use full key: value pair, which makes
stuff more explicit, like:
System:
Host: yawn
Kernel: 5.16.0-11.1-liquorix-amd64
arch: x86_64
bits: 64
compiler: gcc
v: 11.2.0
Desktop: Xfce
v: 4.16.0
tk: Gtk
v: 3.24.24
info: xfce4-panel
wm: xfwm
v: 4.16.1
vt: 7
dm:
1: LightDM
v: 1.26.0
2: SDDM
note: stopped
Distro: Debian GNU/Linux bookworm/sid
12. Fix for mageia and lsb distro data, force use of os-release for mageia if
detected. That overrides the forced use of lsb release for mandrake/mandriva,
because for some reason mageia has decided to carry ALL the legacy distro files:
'/etc/lsb-release',
'/etc/lsb-release.d',
'/etc/mageia-release',
'/etc/mandrake-release',
'/etc/mandrakelinux-release',
'/etc/mandriva-release',
'/etc/os-release',
'/etc/redhat-release',
'/etc/system-release'
which is really not what this stuff is intended for, if it's an actual derived
distro from a living base, then yes, include the base file, but all these have
the same distro id data for mageia, none for the derived distros.
Also, fixed an lsb release thing to avoid using codename if codename contains
release number as well. Since lsb_release is totally legacy at this point, who
cares if we might miss a specific codename here and there on legacy system.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added Color Characteristics to EDID parser, for some reason that had been
left out.
2. Added advanced EDID output option --edid, that allows for showing more
advanced EDID data than is appropriate for most users cases. Ihcludes errors,
color characteristics chroma: (chromacity), full modes, not just min/max.
3. In --slots, added bus-ID.
Also extended report quality, made more granular, got rid of single blob from
Type and Designation and now get more accurate and useful data.
4. In cases with > 1 DM, check to see if one or more are stopped or disabled, =
and add (stopped) if it was detected in running service as stopped.
--------------------------------------------------------------------------------
CHANGES:
1. Reversed monitor ID and mapped: ID values, that was a mistake, the mapped:
item was supposed to contain the X.org mapped name, and the primary ID was
supposed to be the actual real ID the kernel uses. Not a huge deal either way,
but there it is.
2. Include disabled but connected Monitors. This works around nvidia bug showing
monitors disabled when they are enabled, but also allows for showing connected
monitors, though without as much data.
3. Made the last holdout -S > -Sa use strict full key: value pair output, like
Desktop: XFCE v: 4.14.12 and so on.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added help/man for --edid info.
--------------------------------------------------------------------------------
CODE:
1. In ParseEDID: made new key: edid_error, which contains an array ref of 1 or
more edid errors. The previous version did a poor job and returned only the
first error found, so there could have been > 1 error, and you'd never know it.
This changes check_parsed_edid to _check_parsed_edid(). and adds a utility tool
_edid_error, which grabs the message from main::message, giving better output
integration.
This also allows for future error handling expansion quite easily.
2. In map_monitor_ids() fixed matching pattern, made more robust and explicit,
to catch things like s: eDP-1 d: eDP or eDP-1-1, both have been seen. Also added
fallback for single monitor, just map them to eachother if mapping failed.
3. get_pci_vendor() added test for using anything that is 1 character length,
to not break on 1 character length string matches.
4. Fully refactored --slots, that was originally written purely as a proof of
concept in terms of adding a new feature during the original inxi 2.9 rewrite,
and was never actually touched after that.
2022-03-24 18:45:05 +00:00
|
|
|
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
.TP
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.B \-x \-t\fR (\fB\-\-processes\fR)
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Adds memory use output to CPU (\fB\-xt c\fR), and CPU use to memory
|
|
|
|
|
(\fB\-xt m\fR).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-x \-w \fR, \fB\-W\fR
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
\- Adds humidity and barometric pressure.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Adds wind speed and direction.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-A\fR
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds vendor:product ID for each device.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe speed and lanes item (Linux only, if detected).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
|
|
|
|
|
|
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 21:48:52 +00:00
|
|
|
\- Adds \fBwith: [item] \fBstatus: [state/plugin]\fR helper daemons/plugins for
|
|
|
|
|
the sound API/server.
|
|
|
|
|
|
2012-10-19 19:28:31 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-B\fR
|
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 21:18:45 +00:00
|
|
|
\- Adds current power use, in watts.
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- Adds serial number.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new man page. Bug fix, enhancements, fixes.
Bugs:
1. Big bug found on certain systems, they use non system memory memory arrays, inxi
failed to anticipate that situation, and would exit with error when run as root for
-m when it hit those array types. These arrays did not have modules listed, so the
module array was undefined, which caused the failure. Thanks Manjaro anonymous
debugger dataset 'loki' for finding this failure.
This is literally the first dataset I've seen that had this issue, but who knows
how many other system boards will show something like that as well.
Fixes:
1. Related to bug 1, do not show the max module size item if not system memory
and size is less than 10 MiB. Assuming there that it's one of these odd boards.
Enhancements:
1. For bug 1, extended Memory: report to include array type if not system memory.
That instance had Video Memory, Flash Memory, and Cache Memory arrays along with
the regular System Memory array. Now shows: use: Video Memory for example if not
System Memory to make it clear what is going on.
2. Added basic Parrot system base, but for some inexplicable reason, Parrot changed
the /etc/debian_version file to show 'stable' instead of the release number. Why?
Who knows, it would be so much easier if people making these derived distros would
be consistent and not change things for no good reason.
3. Added a few more pattern matches to existing vendors for disks. As usual, thanks
linuxlite/linux hardware database for the endless lists of disk data.
4. Added internal dmidecode debugger switches, that makes it much easier to inject
test dmidecode data from text files using debugger switches internally.
5. Added -Cxx item, which will run if root and -C are used, now grabs L1 and L3
cache data from dmidecode and shows it. I didn't realize that data was there, not
sure how I'd missed it all these years, I guess pinxi really is much easier to work
on! This only runs if user has dmidecode permissions from root or sudo.
2018-09-10 22:13:52 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-D\fR
|
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 18:59:56 +00:00
|
|
|
\- Adds HDD/SSD drive serial number.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds drive speed (if available). This is the theoretical top speed of the
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
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
|
New version, new tarball.
This version is very peaceful, no big changes, just a few fixes and small new
features added.
This version corrects a few small glitches reported by users, and adds basic support
for disk speed report. Note that this is not as accurate as I'd like, it tries, but
there is not a lot of data to be had. Limits of disk speed seems to be, roughly:
1. most speed is reported as max board can do, not max drive can support
2. usually when speed is reported as lower than max board speed, it's correct, but,
as usual, exceptions to this were found during testing.
3. usually if drive is faster than board speed, it reports board speed, but, again,
exceptions to this rule were found during testing.
However, with this said, it's usually more or less right, at least right in terms
of the fastest speed you can expect to get with your board. NVMe was also supported,
that's much more complicated because NVMe has >= 1 lane, and each lane has up and
down data. The reported speed is max in one direction, and is a function of the
PCIe 1,2 20% overhead, and PCIe 3,4,5 ~1.5% overhead. inxi shows the actual usable
data rate, not the GT/s rate, which is the total transfers per second the unit
supports.
So due to the unreliable nature of the data, this is only a -xx option. There is
also in general no data for USB, and none for mmcblk (sd cards usually).
This feature may be enhanced with a C Perl XS library in the future, we'll see how
that goes.
FIXES:
1. corrected an issue where a networking card of type Bridge failed to be detected.
This is now handled. This was a PCI type I'd never seen before, but it exists, and
a user had it, so now it will work as expected for this type.
2. changed the default units in weather to be m (metric) imperial (i). While this is
not very intuitive for me, it's easier to explain I think. The previous c / f
syntax is supported internally, and inxi will just translate c to m and f to i, so
it doesn't matter which is or was used on a config file or with the --weather-unit
option.
3. BSD uptime had a parsing glitch, there was a spelling variant I'd never seen in
GNU/Linux that broke the regex. This is corrected now.
4. Fixed a few small man page glitches, some ordering stuff, nothing major.
5. Fixed BSD hostname issues. There was a case where a setup could have no hostname,
inxi did not handle that correctly. This fix would have applied to gnu/linux as
well.
6. Fixed a few bsd, openbsd mostly, dm detections, there is a secondary path in
OpenBSD that was not checked. This also went along with refactoring the dm logic
to be much more efficient and optimized.
7. Fine tuned dmidecode error message.
8. Fixed PCI ID issue, it was failing to catch a certain bridged network type.
9. A more global fix for unhandled tmpfs types, in this case, shm, but added a
global test that will handle all tmpfs from now on, and exclude that data from
-p reports.
NEW FEATURES:
1. First attempt to add basic disk speed (Gb/s). Supported types: ATA, NVMe. No
speed data so far handled or found: mmcblk; USB. Also possibly older /dev/hda
type devices (IDE bus) may not get handled in all cases. This may get more work
in the future, but that's a long ways off. This case oddly was one where BSDs had
support for basic disk speed reports before GNU/Linux, but that was really just
because it was part of a single data line that inxi parsed for disk data anyway
with BSDs.
2. Man items added for -Dxx disk speed options.
2018-05-21 21:45:09 +00:00
|
|
|
its design speed.
|
|
|
|
|
|
|
|
|
|
NVMe drives: adds lanes, and (per direction) speed is calculated with
|
|
|
|
|
lane speed * lanes * PCIe overhead. PCIe 1 and 2 have data rates of
|
2021-08-25 03:39:33 +00:00
|
|
|
GT/s * .8 = Gb/s (10 bits required to transfer 8 bits of data).
|
New version, new tarball.
This version is very peaceful, no big changes, just a few fixes and small new
features added.
This version corrects a few small glitches reported by users, and adds basic support
for disk speed report. Note that this is not as accurate as I'd like, it tries, but
there is not a lot of data to be had. Limits of disk speed seems to be, roughly:
1. most speed is reported as max board can do, not max drive can support
2. usually when speed is reported as lower than max board speed, it's correct, but,
as usual, exceptions to this were found during testing.
3. usually if drive is faster than board speed, it reports board speed, but, again,
exceptions to this rule were found during testing.
However, with this said, it's usually more or less right, at least right in terms
of the fastest speed you can expect to get with your board. NVMe was also supported,
that's much more complicated because NVMe has >= 1 lane, and each lane has up and
down data. The reported speed is max in one direction, and is a function of the
PCIe 1,2 20% overhead, and PCIe 3,4,5 ~1.5% overhead. inxi shows the actual usable
data rate, not the GT/s rate, which is the total transfers per second the unit
supports.
So due to the unreliable nature of the data, this is only a -xx option. There is
also in general no data for USB, and none for mmcblk (sd cards usually).
This feature may be enhanced with a C Perl XS library in the future, we'll see how
that goes.
FIXES:
1. corrected an issue where a networking card of type Bridge failed to be detected.
This is now handled. This was a PCI type I'd never seen before, but it exists, and
a user had it, so now it will work as expected for this type.
2. changed the default units in weather to be m (metric) imperial (i). While this is
not very intuitive for me, it's easier to explain I think. The previous c / f
syntax is supported internally, and inxi will just translate c to m and f to i, so
it doesn't matter which is or was used on a config file or with the --weather-unit
option.
3. BSD uptime had a parsing glitch, there was a spelling variant I'd never seen in
GNU/Linux that broke the regex. This is corrected now.
4. Fixed a few small man page glitches, some ordering stuff, nothing major.
5. Fixed BSD hostname issues. There was a case where a setup could have no hostname,
inxi did not handle that correctly. This fix would have applied to gnu/linux as
well.
6. Fixed a few bsd, openbsd mostly, dm detections, there is a secondary path in
OpenBSD that was not checked. This also went along with refactoring the dm logic
to be much more efficient and optimized.
7. Fine tuned dmidecode error message.
8. Fixed PCI ID issue, it was failing to catch a certain bridged network type.
9. A more global fix for unhandled tmpfs types, in this case, shm, but added a
global test that will handle all tmpfs from now on, and exclude that data from
-p reports.
NEW FEATURES:
1. First attempt to add basic disk speed (Gb/s). Supported types: ATA, NVMe. No
speed data so far handled or found: mmcblk; USB. Also possibly older /dev/hda
type devices (IDE bus) may not get handled in all cases. This may get more work
in the future, but that's a long ways off. This case oddly was one where BSDs had
support for basic disk speed reports before GNU/Linux, but that was really just
because it was part of a single data line that inxi parsed for disk data anyway
with BSDs.
2. Man items added for -Dxx disk speed options.
2018-05-21 21:45:09 +00:00
|
|
|
PCIe 3 and greater transfer data at a rate of GT/s * 128/130 * lanes = Gb/s
|
|
|
|
|
(130 bits required to transfer 128 bits of data).
|
|
|
|
|
|
|
|
|
|
For a PCIe 3 NVMe drive, with speed of \fB8 GT/s\fR and \fB4\fR lanes
|
|
|
|
|
(\fB8GT/s * 128/130 * 4 = 31.6 Gb/s\fR):
|
|
|
|
|
|
|
|
|
|
\fBspeed: 31.6 Gb/s lanes: 4\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds HDD/SSD drive duid, if available. Some BSDs have it.
|
|
|
|
|
|
|
|
|
|
\- Adds for USB drives USB rev, speed, lanes (lanes Linux only).
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xx \-E\fR (\fB\-\-bluetooth\fR)
|
|
|
|
|
\- Adds vendor:product ID of each device.
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe speed and lanes item (Linux only, and if PCIe bluetooth, which is
|
|
|
|
|
rare).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- Adds (\fBhciconfig \fRonly) LMP subversion (and/or HCI revision if
|
|
|
|
|
applicable) for each device.
|
|
|
|
|
|
New version, new tarball.
This version is very peaceful, no big changes, just a few fixes and small new
features added.
This version corrects a few small glitches reported by users, and adds basic support
for disk speed report. Note that this is not as accurate as I'd like, it tries, but
there is not a lot of data to be had. Limits of disk speed seems to be, roughly:
1. most speed is reported as max board can do, not max drive can support
2. usually when speed is reported as lower than max board speed, it's correct, but,
as usual, exceptions to this were found during testing.
3. usually if drive is faster than board speed, it reports board speed, but, again,
exceptions to this rule were found during testing.
However, with this said, it's usually more or less right, at least right in terms
of the fastest speed you can expect to get with your board. NVMe was also supported,
that's much more complicated because NVMe has >= 1 lane, and each lane has up and
down data. The reported speed is max in one direction, and is a function of the
PCIe 1,2 20% overhead, and PCIe 3,4,5 ~1.5% overhead. inxi shows the actual usable
data rate, not the GT/s rate, which is the total transfers per second the unit
supports.
So due to the unreliable nature of the data, this is only a -xx option. There is
also in general no data for USB, and none for mmcblk (sd cards usually).
This feature may be enhanced with a C Perl XS library in the future, we'll see how
that goes.
FIXES:
1. corrected an issue where a networking card of type Bridge failed to be detected.
This is now handled. This was a PCI type I'd never seen before, but it exists, and
a user had it, so now it will work as expected for this type.
2. changed the default units in weather to be m (metric) imperial (i). While this is
not very intuitive for me, it's easier to explain I think. The previous c / f
syntax is supported internally, and inxi will just translate c to m and f to i, so
it doesn't matter which is or was used on a config file or with the --weather-unit
option.
3. BSD uptime had a parsing glitch, there was a spelling variant I'd never seen in
GNU/Linux that broke the regex. This is corrected now.
4. Fixed a few small man page glitches, some ordering stuff, nothing major.
5. Fixed BSD hostname issues. There was a case where a setup could have no hostname,
inxi did not handle that correctly. This fix would have applied to gnu/linux as
well.
6. Fixed a few bsd, openbsd mostly, dm detections, there is a secondary path in
OpenBSD that was not checked. This also went along with refactoring the dm logic
to be much more efficient and optimized.
7. Fine tuned dmidecode error message.
8. Fixed PCI ID issue, it was failing to catch a certain bridged network type.
9. A more global fix for unhandled tmpfs types, in this case, shm, but added a
global test that will handle all tmpfs from now on, and exclude that data from
-p reports.
NEW FEATURES:
1. First attempt to add basic disk speed (Gb/s). Supported types: ATA, NVMe. No
speed data so far handled or found: mmcblk; USB. Also possibly older /dev/hda
type devices (IDE bus) may not get handled in all cases. This may get more work
in the future, but that's a long ways off. This case oddly was one where BSDs had
support for basic disk speed reports before GNU/Linux, but that was really just
because it was part of a single data line that inxi parsed for disk data anyway
with BSDs.
2. Man items added for -Dxx disk speed options.
2018-05-21 21:45:09 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-G\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Triggers much more complete Screen/Monitor output.
|
|
|
|
|
|
|
|
|
|
\fBX.org:\fR requires \fBxdpyinfo\fR or \fBxrandr\fR, and the advanced per
|
|
|
|
|
monitor feature requires \fBxrandr\fR.
|
|
|
|
|
|
|
|
|
|
\fBWayland:\fR requires any tool capable of showing monitor and resolution
|
|
|
|
|
information. \fBSway\fR has \fBswaymsg\fR, \fBweston\-info\fR or
|
|
|
|
|
\fBwayland\-info\fR can show Wayland information on any Wayland compositor, and
|
|
|
|
|
\fBwlr\-randr\fR can show Wayland information for any \fBwlroots\fR based
|
|
|
|
|
compositor.
|
|
|
|
|
|
|
|
|
|
Further note that all references to \fBDisplays\fR, \fBScreens\fR, and
|
|
|
|
|
\fBMonitors\fR are referring to the \fBX\fR or \fBWayland\fR technical terms,
|
|
|
|
|
not normal consumer usage.
|
|
|
|
|
|
|
|
|
|
\fBX.org:\fR 1 \fBDisplay\fR runs 1 or more \fBScreens\fR, and 1 \fBScreen\fR
|
|
|
|
|
runs 1 or more \fBMonitors\fR.
|
|
|
|
|
|
|
|
|
|
\fBWayland:\fR The \fBDisplay\fR is the primary container, and it can contain 1
|
|
|
|
|
or more \fBMonitors\fR.
|
|
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds vendor:product ID of each device.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe speed and lanes item (Linux only, and if PCIe device and detected).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds output port IDs, active, off (connected but disabled, like a closed
|
|
|
|
|
laptop lid) and empty. Example:
|
2017-06-09 19:39:43 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fBports: active: DVI\-I\-1,VGA\-1 empty: HDMI\-A\-1\fR
|
|
|
|
|
|
|
|
|
|
\- Adds \fBDisplay\fR ID. X.org: the Display running the Screen that runs the
|
|
|
|
|
Monitors; Wayland: the Display that runs the monitors.
|
|
|
|
|
|
|
|
|
|
\- Adds compositor, if found (always shows for Wayland).
|
|
|
|
|
|
|
|
|
|
\- \fBWayland:\fR Adds to \fBDisplay\fR \fBd-rect:\fR if > 1 monitors in
|
|
|
|
|
Display. This is the size of the rectangle Wayland creates to situate the
|
|
|
|
|
monitors in.
|
|
|
|
|
|
|
|
|
|
\- \fBX.org:\fR If available, shows \fBalternate:\fR Xorg drivers. This means a
|
|
|
|
|
driver on the default list of drivers Xorg automatically checks for the device,
|
|
|
|
|
but which is not installed. For example, if you have \fBnouveau\fR driver,
|
|
|
|
|
\fBnvidia\fR would show as alternate if it was not installed. Note that
|
|
|
|
|
\fBalternate:\fR does NOT mean you should have it, it's just one of the drivers
|
|
|
|
|
Xorg checks to see if is present and loaded when checking the device. This can
|
|
|
|
|
let you know there are other driver options. Note that if you have explicitly
|
|
|
|
|
set the driver in \fBxorg.conf\fR, Xorg will not create this automatic check
|
|
|
|
|
driver list.
|
|
|
|
|
|
|
|
|
|
\- \fBXorg:\fR Adds total number of \fBScreens\fR listed for the current
|
|
|
|
|
\fBDisplay\fR.
|
|
|
|
|
|
|
|
|
|
\- \fBXorg:\fR Adds default \fBScreen\fR ID if Screen (not monitor!) total is
|
|
|
|
|
greater than 1.
|
|
|
|
|
|
|
|
|
|
\- \fBX.org:\fR Adds \fBScreen\fR line, which includes the ID (\fBScreen: 0\fR)
|
|
|
|
|
then \fBs-res\fR (Screen resolution), \fBs\-dpi\fR. Remember, this is an Xorg
|
|
|
|
|
\fBScreen\fR, NOT a monitor screen, and the information listed is about the Xorg
|
|
|
|
|
Screen! It may at times be the same as a single monitor system, but usually it's
|
|
|
|
|
different in some ways. Note that the physical monitor dpi and the Xorg dpi are
|
|
|
|
|
not necessarily the same thing, and can vary widely.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds \fBMonitor\fR lines. Monitors are a subset of a \fBScreen\fR (X.org) or
|
|
|
|
|
\fBDisplay\fR (Wayland), each of which can have one or more monitors. Normally a
|
|
|
|
|
dual monitor setup is 2 monitors run by one Xorg Screen/Wayland Display.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- \fBpos: [primary,]{position string|row\-col}\fR (X.org: requires
|
|
|
|
|
\fBxrandr\fR; Wayland: requires \fBswaymsg\fR [sway], \fBwlr\-randr\fR [wlroots
|
|
|
|
|
based compositors], \fBweston\-info\fR / \fBwayland\-info\fR [all]). Uses either
|
|
|
|
|
explicit \fBprimary\fR value or +0+0 position if no primary monitor value set.
|
|
|
|
|
\fBpos:\fR does not show for single monitor setups, or if no position data was
|
|
|
|
|
found.
|
|
|
|
|
|
|
|
|
|
Position is text (left, center, center-l, center\-r, right, top, top\-left,
|
|
|
|
|
top\-center, top\-right, middle, middle\-c, middle\-r, bottom, bottom\-l,
|
|
|
|
|
bottom\-c, bottom\-r) if monitors fit within the following grids: 1x2, 1x3, 1x4,
|
|
|
|
|
2x1, 2x2, 2x3, 3x1, 3x2, 3x3. If layout not supported in text, uses
|
|
|
|
|
[row\-nu]\-[column\-nu] instead to indicate the monitor's position in its grid.
|
|
|
|
|
|
|
|
|
|
The position is based on the upper left corner of each monitor relative to the
|
|
|
|
|
grid of monitors that the \fBXorg\fR \fBScreen\fR is composed of.
|
|
|
|
|
|
|
|
|
|
\- \fBdiag:\fR monitor screen diagonal in mm (inches). Note that this is the
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
\fBv: 3.3 Mesa 11.2.0 compat\-v: 3.0\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-I\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds init type version number (and rc if present).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Adds other detected installed gcc versions (if present).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
\- Adds system default runlevel/target, if detected. Supports Systemd / Upstart
|
|
|
|
|
/SysVinit type defaults.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\- Shows \fBPackages:\fR counts by discovered package manager types (\fBpm:\fR).
|
|
|
|
|
In cases where only 1 pm had results, does not show total after \fBPackages:\fR.
|
|
|
|
|
Does not show installed package managers with 0 packages. See \fB\-a\fR for full
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
output. Moves to \fBRepos\fR if \fB\-rxx\fR.
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
|
2021-08-25 03:39:33 +00:00
|
|
|
\- Adds parent program (or pty/tty) that started shell, if not IRC client.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-xx \-j\fR (\fB\-\-swap\fR), \fB\-xx \-p\fR, \fB\-xx \-P\fR
|
|
|
|
|
\- Adds swap priority to each swap partition (for \fB\-P\fR) used, and for all
|
|
|
|
|
swap types (for \fB\-j\fR).
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-xx \-J\fR (\fB\-\-usb\fR)
|
|
|
|
|
\- Adds vendor:chip id.
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- 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.
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
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 18:59:56 +00:00
|
|
|
.B \-xx \-L\fR (\fB\-\-logical\fR)
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
\- Adds internal LVM Logical volumes, like raid image and meta data volumes.
|
|
|
|
|
|
|
|
|
|
\- Adds full list of Components, sub\-components, and their physical devices.
|
|
|
|
|
|
|
|
|
|
\- For LVM RAID, adds a RAID report line (if not \fB\-R\fR). Read up on LVM
|
|
|
|
|
documentation to better understand their use of the term 'stripes'.
|
|
|
|
|
|
2013-01-29 00:03:06 +00:00
|
|
|
.TP
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
.B \-xx \-m\fR, \fB\-\-memory\-modules\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds memory device Manufacturer.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
2021-08-25 03:39:33 +00:00
|
|
|
\- Adds memory device Part Number (\fBpart\-no:\fR). Useful for ordering new
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
or replacement memory sticks etc. Part numbers are unique, particularly if you
|
|
|
|
|
use the word \fBmemory\fR in the search as well. With \fB\-xxx\fR, also shows
|
|
|
|
|
serial number.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds single/double bank memory, if data is found. Note, this may not be
|
|
|
|
|
100% right all of the time since it depends on the order that data is found
|
|
|
|
|
in \fBdmidecode\fR output for \fBtype 6\fR and \fBtype 17\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\- Adds, if present, memory array voltage. Only some legacy systems will have
|
|
|
|
|
this data available.
|
|
|
|
|
|
|
|
|
|
\- Adds memory module current configured operating voltage, if available.
|
|
|
|
|
|
2014-08-16 23:24:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-M\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Adds chassis information, if data is available. Also shows BIOS
|
2018-04-04 06:41:06 +00:00
|
|
|
ROM size if using \fBdmidecode\fR.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-N\fR
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds vendor:product ID for each device.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe speed and lanes item (Linux only, and if PCIe device and detected).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
|
|
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xx \-r\fR
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\- Adds to \fBPackages:\fR info. See \fB\-Ixx\fR
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
|
2012-10-19 19:28:31 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-R\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- md\-raid: Adds superblock (if present) and algorithm. If resync,
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
shows progress bar.
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
|
|
|
|
|
\- Hardware RAID: Adds Chip vendor:product ID.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New version, new man. Small new enhancements.
1. Added to -s for ipmi, with -x: voltage 12v,5v,3.3v,vbat; for -xx, dimm/soc p1/p2
voltages
2. enhanced wm: feature, needed more filters and protection against redundant data
3. basic apple osx fixes to keep it from crashing, but I'm not spending any more
time on apple junk unless someone pays me for my time, I can't stand the product or
company, it's the total antitheses of freedom or free software, or even openness.
4. openbsd/bsd fixes: openbsd was failing to get cpu flags due to a small oversight
5. -C now shows bits: for the true bits of cpu, not the kernel bits. This is not
a reliable measurement but should be right about 95+ percent of the time, and
basically all of the time for GNU/Linux on Intel/AMD, most of the time for ARM.
When it doesn't know it does not guess, and shows N/A.
6. bsd fix for usb, was running numeric action on string value
7. fixed stderr tool for program_version, now it's hard-coded in program_values
which removes an unneded regex search for every program version test.
8. Mate detection, switched to using mate-sesssion instead of mate-about, the
latter is not getting updated and has the wrong version number on it.
2018-04-17 20:28:16 +00:00
|
|
|
.B \-xx \-s\fR
|
|
|
|
|
\- Adds DIMM/SOC voltages, if present (\fBipmi\fR only).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new man. Small new enhancements.
1. Added to -s for ipmi, with -x: voltage 12v,5v,3.3v,vbat; for -xx, dimm/soc p1/p2
voltages
2. enhanced wm: feature, needed more filters and protection against redundant data
3. basic apple osx fixes to keep it from crashing, but I'm not spending any more
time on apple junk unless someone pays me for my time, I can't stand the product or
company, it's the total antitheses of freedom or free software, or even openness.
4. openbsd/bsd fixes: openbsd was failing to get cpu flags due to a small oversight
5. -C now shows bits: for the true bits of cpu, not the kernel bits. This is not
a reliable measurement but should be right about 95+ percent of the time, and
basically all of the time for GNU/Linux on Intel/AMD, most of the time for ARM.
When it doesn't know it does not guess, and shows N/A.
6. bsd fix for usb, was running numeric action on string value
7. fixed stderr tool for program_version, now it's hard-coded in program_values
which removes an unneded regex search for every program version test.
8. Mate detection, switched to using mate-sesssion instead of mate-about, the
latter is not getting updated and has the wrong version number on it.
2018-04-17 20:28:16 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-S\fR
|
New version, new man. Changes, bug fixes, enhancements! Don't delay!
Bugs:
1. A real bug, the detection for true path of /dev/root had a mistake in it and
would only have worked in half the cases. This was an easy fix, but a significant
but since it also would lead to the actual root / partition showing in Unmounted.
2. Related to the item Fixes-2, if two USB networking devices were attached,
the second one's bus and chip ID would go on the wrong line of data if -n or -i
option were used. Since that would be the line belonging to the one above,
that obviously was weird and wrong.
3. NEW: latest kernel can show hwmon data in sensors, for example from wifi chip.
This broke CPU temp detection and showed way too high cpu temp, so this fix is
fairly important since new kernels may have this new sensors hwmon syntax.
4. Sensors: IPMI alternate syntax found, also case with no data in expected columns,
just N/A, so now the ipmi sensor logic skips all lines with non numeric values in
the values column. This is what it should have done all along, it was trusting
that values would always exist for the field names it looks for.
Fixes:
1. ARM networking fix. ARM devices like rasberry pi that use usb bus for networking
showed the no data message even though usb networking was right below it. This is
corrected, and now that only shows if both main and usb networking failed for ARM.
2. Big repo fix: while testing distro and Trinity live cds, I discovered that apt is
sometimes used with rpms, which made PCLinuxOS and ALT-Linux Repos item show the
apt files but no data since the pattern was looking for start with deb. Added rpm
to pattern, so all distros that use apt running rpms should now 'just work'.
3. Fixed more distro id things, PCLinuxOS should now show its full distro string.
4. Debugger: Filtered out more blocks of /proc, that data is bloated and messy, found
another case where it collected a vast amount of junk system data from zfs in that
case, just blocked the entire range. I had no idea /proc had so much junk data in it!
5. As noted above, IPMI, yet another alternate syntax for field names. My hope that
IPMI software and sensors will be more logical and consistent than lm-sensors output
is proving to be merely wishful thinking, I think now out of 3 datasets I've gotten,
I've seen 3 variants for syntax, not to mention the ipmi-tool vs ipmi-sensors
differences. So IPMI will be like all sensors stuff, a work in progress, to
be updated with every newly discovered alternate syntax and data set.
Enhancements:
1. Disk vendors, added some, improved pattern detections for others. This feature
is getting better all the time. Thanks linuxlite hw db, easy to scan for missing
vendors in their inxi data.
2. Added more wm, budgie-wm, mwm, variants of kwin and Trinity's Twin, several others,
more refactoring of core wm/desktop code.
3. Added gpu ram and reworked memory logic for rasberry pi, which is the only SBC
I am aware of that uses that tool. Now reports the actual total, and also gpu: for
ram data, so you can tell that the gpu is using part of the total. Again, this comes
from issue #153. Also added that info to man page for -I part.
4. Added more ARM and PCI cleaners for neater and more concise ARM/PCI output.
5. Added Trinity support to Desktop section, this had at least two different detection
methods, but since the first just shows KDE original data, only the second one proved
to be Trinity specific. Happily, the full data is available, toolkit, desktop version,
and wm (Twin).
6. New -G,-A,-R -xxx feature: vendor:. Note that vendor data is very bloated and
messy so it's trimmed down substantially, using a series of filters and rules, and
thus it can contain the following: the actual vendor, like Dell, nothing, the
motherboard vendor/product for board based PCI items, or a complete vendor/product
string if it's unique. I couldn't think of a clean field name that meant:
vendor OR vendor + basic product info OR motherboard + board version OR full
product name, including vendor, so in the end, I just used vendor: but it's not
quite the right term, but nothing else seemed to work better. Testers responded
very enthusiastically about this feature so I guess the vendor: name is ok.
Changes:
1. Biggest change: Drives: HDD: total: the HDD: is now changed to: Local Storage:
This was part of issue #153 and is a good suggestion because HDD generally was used
to refer to hard disks, spinning, but with nvme, m.2, ssd, etc, that term is a bit
dated. 'Local' is because inxi does not include detected remote storage in the totals.
2. The recent --wm option which forced ps as data source for window manager detection
has been reversed, now --wm forces wmctrl and ps aux is preferred. Still falls back
to wm ctrl in case the ps test is null, this is better because I have to add the wm
data manually for each one, whereas wmctrl has an unknown set and probably variable
set of wm. Note that I reversed this because I saw several cases where wmctrl was
wrong, and reported a generic source wm instead of the real one. Since most uses are
not going to even be aware of the wm: feature as enhanced with --wm switch, this
should have no impact on users in general. Since the detected wm name needs to be
know to get assigned to wm: and wm version data, I think it will work better to
have the known variants match with the wm data values, then just fallback to
unknown ones that can get fille in over time as we find wm that people actually
use and that you can get version info on and detect.
Removed:
1. Got rid of tests for GTK compiled with version for many desktops, that test
was always wrong because it did not have any necessary relation to the actual
gtk version the desktop was built out of, and it also almost always returned no
data. Since this is an expensive and slow test, and is always going to be wrong
or empty anyway, I've removed it. My tests showed it taking about 300ms or so
to generate no data, heh.
That's the tk: feature in -S. Note I also found that gnome-shell takes
an absurdly long time to give --version info, the slowest of all such things, 300ms
again, just to show version? Someone should fix that, there's no possible reason
why it should take 300 milliseconds to give a simple version string. Note that
this returns tk: to only returning real data, which in this case means only xfce,
kde, and trinity, which are the only desktops that actually report their toolkit
data. I'll probably remove that code in the future unless I can think of some real
use for gtk version elsewhere, but it's just junk data which doesn't even work.
In the future, I will not try to emulate or guess at desktop toolkits, either they
show the data in a direct form like XFCE or Trinity or KDE do, or I won't waste
resources and execution time making bad guesses using inefficient code and logic.
QT desktops like LXQt I'm leaving in because I believe those will tend to track
more closely the QT version on the system, and the tests for QT version aren't
huge ugly hacks the way they are for GTK, so they aren't as slow or intrusive, but
those may also get removed since they almost never work either. But they are also
slowing down the -Sx process so maybe they should be removed as well, I'll think
about it. Since they only are used on LXQt and razer-qt, it probably isn't a big
deal overall.
2018-07-12 21:35:09 +00:00
|
|
|
\- Adds display manager (\fBdm\fR) type, if present. If none, shows N/A.
|
|
|
|
|
Supports most known display managers, including gdm, gdm3,
|
New version, new man. Fine tunings.
New features:
1. for a very few systems that have wmctrl installed, will shows -xxx wm if present
Enhancements:
1. made xorg display server and protocols show more consistently with other layout:
Display: x11 server: X.org 1.9.12 drivers: loaded: ...
if no display protocol found:
Display: server: X.org 1.9.12 drivers: loaded: ...
This brings the -G in line with the other lines, of not putting different data types
inside of parentheses as much as possible. -I still has two of these, but so far it's
not clear how to otherwise show SSH or su/sudo/login in their respective spaces.
Debugger data collector also has something I should have added ages ago, gz filename
now includes the basic 2 digit inxi version number, like 3.0 at end, so I can readily
determine the debugger inxi version, and thus avoid having to root through lots of
versions to find new stuff.
These are all largely cosmetic improvements, or debugger adjustments, except for -Sxxx
now offering wm: if present.
Also changed Desktop: name... (toolkit data) to: Desktop: name... tk: toolkit data
to be more consistent, while not adding great length to the output.
These two changes should also help export to json/xml since that puts unique key/values
back into key value pairs, not merging two together.
2018-04-12 20:23:46 +00:00
|
|
|
idm, kdm, lightdm, lxdm, mdm, nodm, sddm, slim, tint, wdm, and xdm.
|
New version, new man. Several bug fixes, enhancements, options.
Bugs:
1. In some cases, -S Desktop showed xfce when it wasn't xfce. This should be largely
corrected now.
2. Big bug: using lxqt-about for lxqt --version, now opens a dialog box, gui,
so removed that, and now checking lxqt-session for version info instead.
Fixes:
1. Now calling hitachi hgst drives vendor: HGST (Hitachi) to differentiate between
regular Hitachi and HGST hitachi. Added a few more disk vendors.
2. Distro base and core: added linuxlite, elementary. Some distros use:
/etc/upstream-release/lsb-release so testing for that and os-release now too.
3. Extended qt detections, may catch a few stray ones now in non kde qt
desktops.
4. Complete refactor of desktop, desktop info, wm, and -G compositor, now much
easier to extend each feature and add detections, move order around, etc.
Also moved wm to -Sxx now that I use fallback ps aux tests, which were themselves
also totally refactored and optimized. Fixed WindowMaker id, which is made more
annoying because they are the only upper/lower case program name, but in at least
debian, the actual program name is wmaker internally.
Also tightened in particular gnome-shell, which was failing to show due to too
restrictive filtering of desktop/vm repeats. Most wm do not contain the desktop
name in the string, gnome-shell does, only one I'm aware of.
5. Removed N/A from wmctrl output, which just means null, which is what we want.
6. Removed gnome-shell from info: since it will now appear in wm: if found. Added
a few -panel items to info:
Enhancements:
1. Showing type: network bridge for -N when it's type 0680, which is an odd pci
type, generally it's a network bridge, but I figured it's best to show that
explicitly to avoid confusion. This extends the 'type:' from just USB.
2. Added more window managers to wm, matchbox, flwm, fvwm2 (used to just use fvwm,
this was wrong, it's its own thing), a few others.
3. Added a few more compositors to -Gxx. kwin_x11 should be the most noticeable,
but added some more obscure ones too. This feature requires more work.
4. Extended ARM syntax to support a new one, path to /sys/device... has an extra
/soc/ in it, that is now handled, all are tested for. Confirmed working. Note that
ARM has to be confirmed fixed on a device by device basis, since there are key
syntax differences in the paths, but it will get easier the more variants that are
discovered. Added another trimmer to cut off \x00|01|02|03 special non printing
characters which show as weird jibbberish in output, for model/serial number.
5. Refactored wm, info, desktop, compositor, now all use @ps_gui, which is all that
is tested against, not the entire ps_cmd array. This drops the possible tests down
massively since the only things in ps_gui will be the actual stuff found that matches
all the patterns required for that system, not all ps items. Added marco, muffin
fixes. Was showing wm: Metacity (Marco) that is not correct, now shows marco, which
then allows to get version too.
5. -Sxxx now shows wm: version as well, which can be of use now and then.
6. --wm added to trip force using of ps data for wm, this can be useful because
I don't know all variants of wmctrl output, so that makes it easier to test.
7. Added finally support for --debug 3, which now shows timers, functions, and args
printed to screen.
8. Added qmake --version to fallback qt detection.
2018-07-08 23:30:15 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds, if run in X, window manager type (\fBwm\fR), if available. Not all
|
|
|
|
|
window managers are supported. Some desktops support using more than one
|
|
|
|
|
window manager, so this can be useful to see what window manager is actually
|
|
|
|
|
running. If none found, shows nothing. Uses a less accurate fallback tool
|
|
|
|
|
\fBwmctrl\fR if \fBps\fR tests fail to find data.
|
New version, new man. Fixes, a few changes, enhancements.
Fixes:
1. Removed /dev/zram type data from swap partitions, since that's ram, it's
not a partition, obviously.
2. More alternate IPMI syntax found, that's clearly going to take a while to have
most syntaxes handled.
3. Small lm-sensors adjustment, fringe cases might scramble up hwmon and gpu
temps, this is now handled.
Enhancements:
1. Added disk vendors, udinfo.
2. Exciting! New Architecture: MIPS! First datasets, confirmed working. This led to
more abstracting of the previously ARM specific logic to be for SOC in general.
3. Related to 2, added in fallback busybox cases for partition data without fs.
4. Added window managers, xmonad, ratpoison, 9dm, gala (for Pantheon), notion,
windowlab
5. Added Pantheon desktop detection. Note, unable to find a way to get version
number.
6. IMPI sensors: added in psu fans, dimm temp.
7. New -Cxxx option: cpu boost (aka turbo), state enabled / disabled, only shows
if system has that option.
Changes:
1. Made toolkit for -S be -xx instead of -x, only Trinity/KDE and XFCE have that
data.
2018-07-17 00:43:43 +00:00
|
|
|
|
|
|
|
|
\- Adds desktop toolkit (\fBtk\fR), if available (Xfce/KDE/Trinity).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xx \-\-slots\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds slot length.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\- Adds slot voltage, if available.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-xx \-w \fR, \fB\-W\fR
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
\- Adds wind chill, heat index, and dew point, if available.
|
|
|
|
|
|
2019-02-08 04:52:41 +00:00
|
|
|
\- Adds cloud cover, rain, snow, or precipitation (amount in previous hour
|
|
|
|
|
to observation time), if available.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, new man. Changes, bug fixes, enhancements! Don't delay!
Bugs:
1. A real bug, the detection for true path of /dev/root had a mistake in it and
would only have worked in half the cases. This was an easy fix, but a significant
but since it also would lead to the actual root / partition showing in Unmounted.
2. Related to the item Fixes-2, if two USB networking devices were attached,
the second one's bus and chip ID would go on the wrong line of data if -n or -i
option were used. Since that would be the line belonging to the one above,
that obviously was weird and wrong.
3. NEW: latest kernel can show hwmon data in sensors, for example from wifi chip.
This broke CPU temp detection and showed way too high cpu temp, so this fix is
fairly important since new kernels may have this new sensors hwmon syntax.
4. Sensors: IPMI alternate syntax found, also case with no data in expected columns,
just N/A, so now the ipmi sensor logic skips all lines with non numeric values in
the values column. This is what it should have done all along, it was trusting
that values would always exist for the field names it looks for.
Fixes:
1. ARM networking fix. ARM devices like rasberry pi that use usb bus for networking
showed the no data message even though usb networking was right below it. This is
corrected, and now that only shows if both main and usb networking failed for ARM.
2. Big repo fix: while testing distro and Trinity live cds, I discovered that apt is
sometimes used with rpms, which made PCLinuxOS and ALT-Linux Repos item show the
apt files but no data since the pattern was looking for start with deb. Added rpm
to pattern, so all distros that use apt running rpms should now 'just work'.
3. Fixed more distro id things, PCLinuxOS should now show its full distro string.
4. Debugger: Filtered out more blocks of /proc, that data is bloated and messy, found
another case where it collected a vast amount of junk system data from zfs in that
case, just blocked the entire range. I had no idea /proc had so much junk data in it!
5. As noted above, IPMI, yet another alternate syntax for field names. My hope that
IPMI software and sensors will be more logical and consistent than lm-sensors output
is proving to be merely wishful thinking, I think now out of 3 datasets I've gotten,
I've seen 3 variants for syntax, not to mention the ipmi-tool vs ipmi-sensors
differences. So IPMI will be like all sensors stuff, a work in progress, to
be updated with every newly discovered alternate syntax and data set.
Enhancements:
1. Disk vendors, added some, improved pattern detections for others. This feature
is getting better all the time. Thanks linuxlite hw db, easy to scan for missing
vendors in their inxi data.
2. Added more wm, budgie-wm, mwm, variants of kwin and Trinity's Twin, several others,
more refactoring of core wm/desktop code.
3. Added gpu ram and reworked memory logic for rasberry pi, which is the only SBC
I am aware of that uses that tool. Now reports the actual total, and also gpu: for
ram data, so you can tell that the gpu is using part of the total. Again, this comes
from issue #153. Also added that info to man page for -I part.
4. Added more ARM and PCI cleaners for neater and more concise ARM/PCI output.
5. Added Trinity support to Desktop section, this had at least two different detection
methods, but since the first just shows KDE original data, only the second one proved
to be Trinity specific. Happily, the full data is available, toolkit, desktop version,
and wm (Twin).
6. New -G,-A,-R -xxx feature: vendor:. Note that vendor data is very bloated and
messy so it's trimmed down substantially, using a series of filters and rules, and
thus it can contain the following: the actual vendor, like Dell, nothing, the
motherboard vendor/product for board based PCI items, or a complete vendor/product
string if it's unique. I couldn't think of a clean field name that meant:
vendor OR vendor + basic product info OR motherboard + board version OR full
product name, including vendor, so in the end, I just used vendor: but it's not
quite the right term, but nothing else seemed to work better. Testers responded
very enthusiastically about this feature so I guess the vendor: name is ok.
Changes:
1. Biggest change: Drives: HDD: total: the HDD: is now changed to: Local Storage:
This was part of issue #153 and is a good suggestion because HDD generally was used
to refer to hard disks, spinning, but with nvme, m.2, ssd, etc, that term is a bit
dated. 'Local' is because inxi does not include detected remote storage in the totals.
2. The recent --wm option which forced ps as data source for window manager detection
has been reversed, now --wm forces wmctrl and ps aux is preferred. Still falls back
to wm ctrl in case the ps test is null, this is better because I have to add the wm
data manually for each one, whereas wmctrl has an unknown set and probably variable
set of wm. Note that I reversed this because I saw several cases where wmctrl was
wrong, and reported a generic source wm instead of the real one. Since most uses are
not going to even be aware of the wm: feature as enhanced with --wm switch, this
should have no impact on users in general. Since the detected wm name needs to be
know to get assigned to wm: and wm version data, I think it will work better to
have the known variants match with the wm data values, then just fallback to
unknown ones that can get fille in over time as we find wm that people actually
use and that you can get version info on and detect.
Removed:
1. Got rid of tests for GTK compiled with version for many desktops, that test
was always wrong because it did not have any necessary relation to the actual
gtk version the desktop was built out of, and it also almost always returned no
data. Since this is an expensive and slow test, and is always going to be wrong
or empty anyway, I've removed it. My tests showed it taking about 300ms or so
to generate no data, heh.
That's the tk: feature in -S. Note I also found that gnome-shell takes
an absurdly long time to give --version info, the slowest of all such things, 300ms
again, just to show version? Someone should fix that, there's no possible reason
why it should take 300 milliseconds to give a simple version string. Note that
this returns tk: to only returning real data, which in this case means only xfce,
kde, and trinity, which are the only desktops that actually report their toolkit
data. I'll probably remove that code in the future unless I can think of some real
use for gtk version elsewhere, but it's just junk data which doesn't even work.
In the future, I will not try to emulate or guess at desktop toolkits, either they
show the data in a direct form like XFCE or Trinity or KDE do, or I won't waste
resources and execution time making bad guesses using inefficient code and logic.
QT desktops like LXQt I'm leaving in because I believe those will tend to track
more closely the QT version on the system, and the tests for QT version aren't
huge ugly hacks the way they are for GTK, so they aren't as slow or intrusive, but
those may also get removed since they almost never work either. But they are also
slowing down the -Sx process so maybe they should be removed as well, I'll think
about it. Since they only are used on LXQt and razer-qt, it probably isn't a big
deal overall.
2018-07-12 21:35:09 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-A\fR
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
\- Adds, if present, serial number.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds, if present, PCI/USB class ID.
|
|
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-B\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Adds battery chemistry (e.g. \fBLi\-ion\fR), cycles (NOTE: there appears to
|
|
|
|
|
be a problem with the Linux kernel obtaining the cycle count, so this almost
|
|
|
|
|
always shows \fB0\fR. There's nothing that can be done about this glitch, the
|
|
|
|
|
data is simply not available as of 2018\-04\-03), location (only available from
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\fBdmidecode\fR derived output).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
\- Adds attached device \fBrechargeable: [yes|no]\fR information.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.TP
|
New version, new man. Fixes, a few changes, enhancements.
Fixes:
1. Removed /dev/zram type data from swap partitions, since that's ram, it's
not a partition, obviously.
2. More alternate IPMI syntax found, that's clearly going to take a while to have
most syntaxes handled.
3. Small lm-sensors adjustment, fringe cases might scramble up hwmon and gpu
temps, this is now handled.
Enhancements:
1. Added disk vendors, udinfo.
2. Exciting! New Architecture: MIPS! First datasets, confirmed working. This led to
more abstracting of the previously ARM specific logic to be for SOC in general.
3. Related to 2, added in fallback busybox cases for partition data without fs.
4. Added window managers, xmonad, ratpoison, 9dm, gala (for Pantheon), notion,
windowlab
5. Added Pantheon desktop detection. Note, unable to find a way to get version
number.
6. IMPI sensors: added in psu fans, dimm temp.
7. New -Cxxx option: cpu boost (aka turbo), state enabled / disabled, only shows
if system has that option.
Changes:
1. Made toolkit for -S be -xx instead of -x, only Trinity/KDE and XFCE have that
data.
2018-07-17 00:43:43 +00:00
|
|
|
.B \-xxx \-C\fR
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
\- Adds CPU voltage and external clock speed (this is the motherboard speed).
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Requires doas/sudo/root and \fBdmidecode\fR.
|
|
|
|
|
|
|
|
|
|
\- Adds, if smt (Simultaneous MultiThreading) data is available, after
|
|
|
|
|
\fBtype:\fR data \fBsmt: [status]\fR.
|
|
|
|
|
.br
|
|
|
|
|
\fBsmt: [status]\fR
|
|
|
|
|
.br
|
|
|
|
|
\fBMT\fR in \fBtype:\fR will show if smt is enabled in general. 3 values are
|
|
|
|
|
possible: [\fBenabled|disabled|<unsupported>\fR]. \fB<unsupported>\fR means the
|
|
|
|
|
CPU does not support SMT.
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
|
New version, new man. Fixes, a few changes, enhancements.
Fixes:
1. Removed /dev/zram type data from swap partitions, since that's ram, it's
not a partition, obviously.
2. More alternate IPMI syntax found, that's clearly going to take a while to have
most syntaxes handled.
3. Small lm-sensors adjustment, fringe cases might scramble up hwmon and gpu
temps, this is now handled.
Enhancements:
1. Added disk vendors, udinfo.
2. Exciting! New Architecture: MIPS! First datasets, confirmed working. This led to
more abstracting of the previously ARM specific logic to be for SOC in general.
3. Related to 2, added in fallback busybox cases for partition data without fs.
4. Added window managers, xmonad, ratpoison, 9dm, gala (for Pantheon), notion,
windowlab
5. Added Pantheon desktop detection. Note, unable to find a way to get version
number.
6. IMPI sensors: added in psu fans, dimm temp.
7. New -Cxxx option: cpu boost (aka turbo), state enabled / disabled, only shows
if system has that option.
Changes:
1. Made toolkit for -S be -xx instead of -x, only Trinity/KDE and XFCE have that
data.
2018-07-17 00:43:43 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xxx \-D\fR
|
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 18:59:56 +00:00
|
|
|
\- Adds HDD/SSD drive firmware revision number (if available).
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds drive partition scheme (in most cases), e.g. \fBscheme: GPT\fR.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Currently not able to detect all schemes, but handles the most common, e.g.
|
|
|
|
|
\fBGPT\fR or \fBMBR\fR.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- 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
|
New version! Fixes!! Bug fixes! More bug fixes!! Cleanups!
Most of these were exposed by issue #251 filed by LukasNickel, then further
revealed via his debugger data set, which showed two more bugs. Well, bugs,
changed syntaxes, same difference to end users.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Work is ongoing to add btrfs support to -R (similar to softraid or zfs),
basic stubs and debuggers added, but reporting tools are not as robust (and
often require sudo/root for reasons that escape me) as I would have hoped, so
it's slow. One of these days... Normally would not release with working stubs,
but there were enough real issues/bugs to warrant just getting 3.3.06 out the
door, then going on with the btrfs feature for -R. But so far I view the
reporting tools as inadequate, unfortunately.
--------------------------------------------------------------------------------
BUGS:
1. As initially discovered in issue #251 there are alternate syntaxes which had
never been seen before for remote mounts, fuse mounts, etc. In this case, it was
fuse.sshfs that was not removed from the Disk total:... used: leading to silly
1000+% used percentage. Note that while technically inxi could try to be clever
about reporting impossible percentages, so far those have led to bugs getting
reported, then fixed, so I think it worth leaving it as is.
2. When --swap/-j is used with no other arguments, failed to show uuid or label.
Discovered this while testing fix 2.
3. Bug which is not a bug but will appear as such to users, nvme temps were
failing in -Dx due to a change in how those values are located in /sys. See fix
3.
--------------------------------------------------------------------------------
FIXES:
1. Going along with Bug 1, and considering that only in 3.3.05 was the nfs4
remote fs failure to identify/exclude, the entire section involving remote/ fuse
etc file systems was refactored, and extended to add many more previously
non-handled remote and fuse type file systems. Significant extension of known
remote filesystem types, distributed file systems, overlay file systems, all to
try to avoid having more distributed/remote/fuse file system issues. Also added
test to support fuse. or fuseblk. type prefixes for any of these. Hopefully
there will be fewer issues related to distributed and remote and overlay type
file systems in the future.
2. Made all label/uuid triggers global, that is, -ol shows unmounted with
labels, -ju shows swap with uuid, and so on. This may require a bit more tweaks
to get exactly right, but in general, this is a purely cosmetic fix, that is,
try not to show label/uuid for partition/mounts that probably can't have those
values.
3. There was a change in the way nvme /sys temperature paths were handled, an
actually understandable, albeit as always annoying, one, because inxi actually
had to do a sort of convoluted hack to get the nvme block devices temperatore
paths before, now that hack is not required for newer kernels (5.12+), though
for kernels that had the old paths (5,8, 5.9 at least, don't know when paths
changed) left in the old method. Now tests are more granular, and inxi should
find temperatures regardless of which method is used for nvme and sd type
drives.
4. Another somewhat irksome random change, again, understandable since the new
syntax is more consistent in output than the previous one, but still breaks all
existing parsers that use the changed field names. Lsblk did NOT change the -o
input field names, but DID change the output field names, which broke the
internal inxi parser, and led to null lsblk data.
Changes were - or : separators in input values are output as _ always. that is,
MAJ:MIN becomes MAJ_MIN. Also corrected the debugger lsblk to use the same
output fields for -P -o as the actual lsblk parser uses internally so these
failures can be spotted more readily, as it was, it was literally only because
someone submitted the debugger dataset, and was running lsblk 2.37, where I
believe this behavior change happened. Solution was to just use regex patterns
instead, [:_-], in the parser. Big fear now is that they will randomly stop
supporting the -o input field names that contain - or : and change that too
without any real warning or deprecation notice.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug and fix 1, added avfs, afs, archivemount, avfs, ceph, gfs,
glusterfs, gmailfs, hdfs, ipfs, kosmos/kfs, lafs, mergerfs, mhddfs, moosefs,
ocfs, openafs, orangefs, overlayfs, pvfs, s3fs, sheepdog, vmfs, and several
others to the exclude list for disk used and show label/uuids for partitions.
2. A smattering of disk vendors added.
--------------------------------------------------------------------------------
CHANGES:
1. Going with fix 2, -l and -u no longer will trigger -P by default, now if -l
or -u are used without -j, -o, -p, -P, an error will explain that you must use
one of those together with -l or -u. This was the only way to get the -l and -u
switches to turn off/on label/uuid reports in swap, unmounted, and partitions
consistently. Triggering -P was really a legacy behavior from when the only
options were -p or -P, and --swap and --unmounted did not exist. I found it
increasingly odd that unmounted would show label/uuid always but partitions only
with -l/-u.
2. This was a pet peeve, sometimes field names just bug me (like 'Topology: did
for CPU, now corrected to Info:), the Drive: rotation: was one such annoyance.
I had recycled that to indicate SSD, which was a feature request, but that was
always a sloppy solution, and made no sense, since SSD isn't a rotation speed.
Now it reports a much more logical:
ID-1:...... type: HDD rpm: 7200
or
ID-1:...... type: SSD
or
ID-1:...... type: N/A
This also corresponds to the intended meaning much better. The HDD type was
always present internally if rotation speed is detected, but was not used. Now
will also show type: N/A if reliable type detection failed, which will also be
more consistent.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Brought most of inxi.changelog (this file) into a consistent state, re
whitespaces, readability, consistent use of various header / section names.
Ideally while I don't expect anyone to ever sit down and read this changelog, it
will be now much easier to scan to find whatever interests you. This change goes
along with ongoing changes in docs to in general try to be usually 80 columns
wide.
2. inxi-resources.txt, inxi-data.txt are updated with more raid, partition, file
system values and data to go along with bug, fix, enhancement 1.
3. Man and help updated to indicate -u and -l no longer trigger -P by default.
--------------------------------------------------------------------------------
CODE:
1. Ongoing refactors, bringing the codebase to the point that matches current
coding styles. Removed remainder of whitespaces in conditions and for/while
loops, for example:
if ( condition ) {
becomes:
if (condition){
and
if ( ( test set 1 ) && ( test set 2 ) ) {
becomes:
if ((test set 1) && (test set 2)){
and so on. That dropped over 2 KiB of whitespaces. This went along with fixes
that have been ongoing to change to this whitespace use style, but previously it
was only being done when that situation was hit in a local block, now it's been
completed globally.
This continues the style refactor that has been ongoing for a while now, to
bring inxi into a consistent state, since when it started, it was more pressing
to get the bash/gawk mess translated to Perl than it was to get the Perl itself
to be as good/consistent as possible, so now those issues are being slowly
unravelled, and hopefully will set inxi on course for its next 10 years.
It was starting to get annoying, because some parts of inxi used those spaces,
and all newer ones didn't in general. Now it's one behavior throughout the whole
program file.
2. Refactored the entire fs exclude for disk used data, and integrated those
values into a global tool that is used either to exclude file systems from disk
used totals, or to not show uuid/labels for the excluded
remote/distributed/overlay type file systems, which in general don't have uuid
or labels.
2021-07-22 03:30:58 +00:00
|
|
|
identification was made. If no HDD, rotation, or positive SSD ID found, shows
|
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 18:59:56 +00:00
|
|
|
\fBtech: N/A\fR. Not all HDD spinning disks report their speed, so even if they
|
2021-08-25 03:39:33 +00:00
|
|
|
are spinning, no rpm data will show.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-E\fR (\fB\-\-bluetooth\fR)
|
|
|
|
|
\- Adds, if present, PCI/USB class ID.
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- Adds, if present, bluetooth device class ID.
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- Adds (\fBhciconfig \fRonly) HCI version, revision.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-G\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds, if present, Device PCI/USB class ID.
|
|
|
|
|
|
|
|
|
|
\- Adds to Device \fBserial:\fR number (if found).
|
|
|
|
|
|
|
|
|
|
\- \fBXorg:\fR Adds to \fBScreen:\fR \fBs\-size:\fR and \fBs\-diag:\fR. (Screen
|
|
|
|
|
size data requires \fBxdpyinfo\fR). This is the X.org Screen dimensions, NOT the
|
|
|
|
|
Monitor size!
|
|
|
|
|
|
|
|
|
|
\- Adds to Monitors (if detected) frequency (\fBhz:\fR).
|
|
|
|
|
|
|
|
|
|
\- Adds to Monitors (if detected) size (\fBsize: 277x156mm (10.9x6.1")\fR). Note
|
|
|
|
|
that this is the real physical monitor size, not the Xorg Screen/Wayland Display
|
|
|
|
|
size, which can be quite different (1 Xorg Screen / Wayland Display can for
|
|
|
|
|
instance contain two or more monitors).
|
|
|
|
|
|
|
|
|
|
\- Adds to Monitors \fBmodes: min: max:\fR (if detected). These are the smallest
|
|
|
|
|
and largest monitor modes found, using an inexact method, so might not always be
|
|
|
|
|
right.
|
|
|
|
|
|
|
|
|
|
\- Adds to Monitors \fBserial:\fR number (if detected).
|
|
|
|
|
|
|
|
|
|
\- \fBWayland:\fR Adds to Monitors \fBscale:\fR (if detected).
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
New version, new man. Changes, bug fixes, enhancements! Don't delay!
Bugs:
1. A real bug, the detection for true path of /dev/root had a mistake in it and
would only have worked in half the cases. This was an easy fix, but a significant
but since it also would lead to the actual root / partition showing in Unmounted.
2. Related to the item Fixes-2, if two USB networking devices were attached,
the second one's bus and chip ID would go on the wrong line of data if -n or -i
option were used. Since that would be the line belonging to the one above,
that obviously was weird and wrong.
3. NEW: latest kernel can show hwmon data in sensors, for example from wifi chip.
This broke CPU temp detection and showed way too high cpu temp, so this fix is
fairly important since new kernels may have this new sensors hwmon syntax.
4. Sensors: IPMI alternate syntax found, also case with no data in expected columns,
just N/A, so now the ipmi sensor logic skips all lines with non numeric values in
the values column. This is what it should have done all along, it was trusting
that values would always exist for the field names it looks for.
Fixes:
1. ARM networking fix. ARM devices like rasberry pi that use usb bus for networking
showed the no data message even though usb networking was right below it. This is
corrected, and now that only shows if both main and usb networking failed for ARM.
2. Big repo fix: while testing distro and Trinity live cds, I discovered that apt is
sometimes used with rpms, which made PCLinuxOS and ALT-Linux Repos item show the
apt files but no data since the pattern was looking for start with deb. Added rpm
to pattern, so all distros that use apt running rpms should now 'just work'.
3. Fixed more distro id things, PCLinuxOS should now show its full distro string.
4. Debugger: Filtered out more blocks of /proc, that data is bloated and messy, found
another case where it collected a vast amount of junk system data from zfs in that
case, just blocked the entire range. I had no idea /proc had so much junk data in it!
5. As noted above, IPMI, yet another alternate syntax for field names. My hope that
IPMI software and sensors will be more logical and consistent than lm-sensors output
is proving to be merely wishful thinking, I think now out of 3 datasets I've gotten,
I've seen 3 variants for syntax, not to mention the ipmi-tool vs ipmi-sensors
differences. So IPMI will be like all sensors stuff, a work in progress, to
be updated with every newly discovered alternate syntax and data set.
Enhancements:
1. Disk vendors, added some, improved pattern detections for others. This feature
is getting better all the time. Thanks linuxlite hw db, easy to scan for missing
vendors in their inxi data.
2. Added more wm, budgie-wm, mwm, variants of kwin and Trinity's Twin, several others,
more refactoring of core wm/desktop code.
3. Added gpu ram and reworked memory logic for rasberry pi, which is the only SBC
I am aware of that uses that tool. Now reports the actual total, and also gpu: for
ram data, so you can tell that the gpu is using part of the total. Again, this comes
from issue #153. Also added that info to man page for -I part.
4. Added more ARM and PCI cleaners for neater and more concise ARM/PCI output.
5. Added Trinity support to Desktop section, this had at least two different detection
methods, but since the first just shows KDE original data, only the second one proved
to be Trinity specific. Happily, the full data is available, toolkit, desktop version,
and wm (Twin).
6. New -G,-A,-R -xxx feature: vendor:. Note that vendor data is very bloated and
messy so it's trimmed down substantially, using a series of filters and rules, and
thus it can contain the following: the actual vendor, like Dell, nothing, the
motherboard vendor/product for board based PCI items, or a complete vendor/product
string if it's unique. I couldn't think of a clean field name that meant:
vendor OR vendor + basic product info OR motherboard + board version OR full
product name, including vendor, so in the end, I just used vendor: but it's not
quite the right term, but nothing else seemed to work better. Testers responded
very enthusiastically about this feature so I guess the vendor: name is ok.
Changes:
1. Biggest change: Drives: HDD: total: the HDD: is now changed to: Local Storage:
This was part of issue #153 and is a good suggestion because HDD generally was used
to refer to hard disks, spinning, but with nvme, m.2, ssd, etc, that term is a bit
dated. 'Local' is because inxi does not include detected remote storage in the totals.
2. The recent --wm option which forced ps as data source for window manager detection
has been reversed, now --wm forces wmctrl and ps aux is preferred. Still falls back
to wm ctrl in case the ps test is null, this is better because I have to add the wm
data manually for each one, whereas wmctrl has an unknown set and probably variable
set of wm. Note that I reversed this because I saw several cases where wmctrl was
wrong, and reported a generic source wm instead of the real one. Since most uses are
not going to even be aware of the wm: feature as enhanced with --wm switch, this
should have no impact on users in general. Since the detected wm name needs to be
know to get assigned to wm: and wm version data, I think it will work better to
have the known variants match with the wm data values, then just fallback to
unknown ones that can get fille in over time as we find wm that people actually
use and that you can get version info on and detect.
Removed:
1. Got rid of tests for GTK compiled with version for many desktops, that test
was always wrong because it did not have any necessary relation to the actual
gtk version the desktop was built out of, and it also almost always returned no
data. Since this is an expensive and slow test, and is always going to be wrong
or empty anyway, I've removed it. My tests showed it taking about 300ms or so
to generate no data, heh.
That's the tk: feature in -S. Note I also found that gnome-shell takes
an absurdly long time to give --version info, the slowest of all such things, 300ms
again, just to show version? Someone should fix that, there's no possible reason
why it should take 300 milliseconds to give a simple version string. Note that
this returns tk: to only returning real data, which in this case means only xfce,
kde, and trinity, which are the only desktops that actually report their toolkit
data. I'll probably remove that code in the future unless I can think of some real
use for gtk version elsewhere, but it's just junk data which doesn't even work.
In the future, I will not try to emulate or guess at desktop toolkits, either they
show the data in a direct form like XFCE or Trinity or KDE do, or I won't waste
resources and execution time making bad guesses using inefficient code and logic.
QT desktops like LXQt I'm leaving in because I believe those will tend to track
more closely the QT version on the system, and the tests for QT version aren't
huge ugly hacks the way they are for GTK, so they aren't as slow or intrusive, but
those may also get removed since they almost never work either. But they are also
slowing down the -Sx process so maybe they should be removed as well, I'll think
about it. Since they only are used on LXQt and razer-qt, it probably isn't a big
deal overall.
2018-07-12 21:35:09 +00:00
|
|
|
.TP
|
2018-03-29 03:57:19 +00:00
|
|
|
.B \-xxx \-I\fR
|
Bug fixes, new features!! Update now!! Or don't, it's up to you.
Bugs:
1. Let's call some of the android fixes and debugger failures bugs, why not?
Those are fixed. Note that many of these fixes will impact any system that is
ARM based, not just android.
Fixes:
1. Related to issue #226 which was a fine issue, fine tuned the debugger debuggers
to allow for smoother handling of /sys parse failures. Also added debugger filters
for common items that would make the /sys parser hang, oddly, most seem to be in
/sys/power for android devices.
2. Added some finetunings for possible mmcblk storage paths, in some cases, an
extra /block is added, which made inxi think mounted drives were unmounted. I've
never seen this extra /block except on mmcblk devices on android, but you never
know, it could be more widespread.
3. Also mainly related to android, but maybe other ARM devices, in some cases,
an errant 'timer' device was appearing as a cpu variant, which is wrong. That was
a corner case for sure, and part of the variant logic in fact uses timer values
to assign the actual cpu variants, but it was wrong in this case because it was
....-timer-mem, not ...-timer, which led to non-existent CPU variants showing.
4. Issue #236 by ChrisCheney pointed out that inxi had never updated its default
/proc/meminfo value to use the newer MemAvailable as default if present, which led
to incorrect memory used values showing up. That's because back in the old days,
we had to construct a synthetic Memory used from MemFree, buffers, cache, etc, but that
wasn't always right, since sometimes the cache actually isn't available, often is,
but not always.
https://github.com/torvalds/linux/commit/34e431b0ae398fc54ea69ff85ec700722c9da773
This commit on the kernel explains it pretty clearly.
Thanks Chris for bringing this to our attention.
5. Kind of more future-proofing, got rid of a bunchy of hard-coded strings internally
and switched those to use the row_defaults values, which is where string messages
are supposed to go. That was mostly in the initial program check messages on start-up,
but also a few other stray ones. Also consolidated them a bit to get rid of redundant
messages, and added more variable based messages, like for missing/permissions on
programs etc. The idea in general is that all the strings are contained in subs so
that in theory they could be swapped for other strings, eg, languages, but honestly,
I no longer see this as very likely to ever happen. But it's still nice to be
consistent internally and not get sloppy with english strings.
This also got rid of some largely redundant items in row_defaults, and expanded the
list of handled events, and of variable based events, so it shouldn't be as necessary
to add new row_defaults items for similar events.
Enhancements:
1. Debugger item to maybe try to find distro OEM, this was connected with issue #231
but the issue poster vanished, and didn't do the work required, so this one won't
happen until someone who cares [not me, that is] does the required work.
It's always funny to see how quickly people vanish when they have to do the actual
boring research that they want me to do for them, lol. Or maybe, sigh is more
appropriate than lol. But it is pretty much par for the course, sad to say.
Or maybe this was an OEM hoping to have someone do their corporate work for them
for free, who knows. Anyway, there's a certain category of items that I'm reasonably
happy to implement, but NOT if I have to do all the boring research work, so such
features being added will depend on the poster actually doing the boring work.
I've gotten burned on this a few times, cpu arch: for example, some guy said he'd
track that and provide updates, he never even made it to the first release, so I got
stuck doing that one forever after. But that one at least has some general value, so
that's ok more or less, but I definitely won't take on stuff that I really don't
personally care at all about unless the person requesting the feature does all the work
beforehand. The boring part, that is....
2. Related to issue #226, much improved android ID and many small android fixes for
machine data etc. Now uses /system/build.prop for some data, which is a nice source,
sadly, most modern android devices seem to be locked down, with both build.prop and
/sys locked down, which makes inxi unable to actually get any of that data, but if
your device either does not have these root only readable, or if you have an android
rooted phone, the android support will be more informative.
Hint: if you run inxi in termux on your non rooted android device, and it shows
you what android version you are using in System:... Distro: line, then your android
is not locked down. I have one such phone, android 7.1, but I cannot say how usual
or non usual this is. The poster of issue #226 for instance had to root his android
7 phone to get this data to display. So it seems to vary quite a bit.
Note that due to these file system lockdowns, in general, trying to do android arm
support remains largely a waste of time, but on some devices sometimes, you can now
get quite nice system info. As I noted in the issue, if I can't get the features to
work on a non rooted phone in my possession, I'm probably not going to try to do the
work because it's too hard to try to work on android issues without having the device
in front of you for testing and debugging. In this case, one of my phones did work, so
I did the work just to see where android is at now.
Android showed some slightly odd syntaxes for some devices, but those are now handled
where I got a dataset for them that revealed the changes required.
3. Also related to issue #226 for termux in android, will show -r info.
That's an apt based package manager, but termux puts the apt files somewhere else so
needed to change paths if those alternate paths existed for apt.
4. Added PARTFLAGS to debugger to see what knd of data that will yield, that's
a lsblk key/value pair.
5. Just because it's easy to do, added new -Ixxx item, wakeups: which is a
subset of Uptime, this will show how many times the system has been woken from
suspend since the last boot. If the system has never been suspended, shows 0.
6. Many more disk vendors and disk IDs. The list just never ends, possibly a
metaphor for something, the endless spinning of maya, who knows?
7. Added newest known ubuntu release, hirsute, to buntu ID logic. Might as well
catch them early, that will be 21.04.
2020-11-11 23:35:08 +00:00
|
|
|
\- For \fBUptime:\fR adds \fBwakeups:\fR to show how many times the machine
|
|
|
|
|
has been woken from suspend state during current uptime period (if available,
|
|
|
|
|
Linux only). 0 value means the machine has not been suspended.
|
|
|
|
|
|
2018-03-29 03:57:19 +00:00
|
|
|
\- For \fBShell:\fR adds \fB(su|sudo|login)\fR to shell name if present.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
\- For \fBShell:\fR adds \fBdefault:\fR shell if different from
|
|
|
|
|
running shell, and default shell \fBv:\fR, if available.
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- For \fBrunning\-in:\fR adds \fB(SSH)\fR to parent, if present. SSH detection
|
|
|
|
|
uses the \fBwhoami\fR test.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-J\fR (\fB\-\-usb\fR)
|
|
|
|
|
\- Adds, if present, serial number for non hub devices.
|
|
|
|
|
|
|
|
|
|
\- Adds \fBinterfaces:\fR for non hub devices.
|
|
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds, if present, USB class ID.
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- Adds, if non 0, max power in mA.
|
|
|
|
|
|
2018-03-29 03:57:19 +00:00
|
|
|
.TP
|
New version, many small fixes. And a hall of shame, LOL.
Bugs:
1. Issue #188 exposed a situation in glxinfo where the required opengl fields are
present but contain null data. This happens when a system does not have the required
opengl drivers, which was the case here. inxi failed to handle that. Thanks
LinuxMonger for posting the required data to figure this corner case out.
2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals)
where it was supposed to use regex pattern match. Oops. Would have led to
disk vendor id failures in several cases.
Fixes:
1. help, man updates for RAM/Memory data, more clarifications.
2. Refactored RepoData class/package, to make it easier to handle repo string
data, and make it all overall cleaner internally, and enable future extensions
to certain features in inxi that may or may not one day become active.
3. Added to some regex compares \Q$VAR\E to disable regex characters in strings.
I should have used that a long time ago, oh well, better late than never!
4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual
pixel dimensions, shame on whoever allowed that output!!! shame! Had to add
a workaround to make sure numeric values are present, if not, then use the
fallback, which means, 2x more data parsing to get data that should not
require that, but in this example, it did (an Arch derivative, but it could
be xdpyinfo itself, don't know)>
Enhancements:
1. More fixes on issue #185. Thanks tubecleaner for finding and provding required
data to really solve a set of RAM issues that apply particularly in production
systems. This issue report led to 2 new options: --memory-short, which only
shows a basic RAM report.
Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%)
Report: arrays: 1 slots: 4 modules: 2 type: DDR4
And a 2nd, --memory-modules, only shows the occupied slots. This can be
useful in situations where it's a server or vm with a lot of slots, most empty:
Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%)
Array-1: capacity: 256 GiB slots: 4 EC: None
Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s
Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s
Note that both of these options trigger -m, so -m itself is not required.
2. More disk vendors!! The list never ends! Thanks linux-lite hardware database
and users for supplying, and buying/obtaining, apparently every disk known to
mankind.
3. Added fallback XFCE detection, in cases were the system does not have xprop
installed, it's still possible to do a full detection of xfce, including toolkit,
so now inxi does that, one less dependency to detect one more desktop.
4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this
in the wild, but I did see it as the kernel reported driver from lspci, so it
may exist.
Unfixed:
1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there
is a RAID ZFS issue that will not get fixed until the required debugger data is
supplied. Please do not waste all our time filing an issue if you have no
intention of actually following through so we can get it fixed.
Note that a key way we get issues here is from Perl errors on the screen, which are
a frequent cause of someone realizing something is wrong. This is why I'm not going
to do a hack fix for the RAID ZFS issue, then the error messages will go away, and
it will likely never get handled. For examples of good, useful, productive issue
reports, and how to do them right: #188 and #185, both of which led to good
improvements in how inxi handles corner cases in those areas.
2019-08-14 18:14:13 +00:00
|
|
|
.B \-xxx \-m\fR, \fB\-\-memory\-modules\fR
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds memory bus width: primary bus width, and if present, total width. e.g.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\fBwidth (bits): data: 64 total: 72\fR
|
|
|
|
|
|
|
|
|
|
Note that total / data widths are mixed up sometimes in dmidecode output, so
|
|
|
|
|
inxi will take the larger value as the total if present. \fBData\fR width
|
|
|
|
|
usually corresponds to the CPU bits. \fBTotal\fR can reflect EEC or Dual Channel
|
|
|
|
|
widths. If no total width data is found, shows:
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\fBwidth: N/A\fR
|
|
|
|
|
|
|
|
|
|
\- Adds device type detail, e.g. \fBtype: DDR3 detail: Synchronous\fR.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- Adds device serial number.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
\- Adds memory module current, max, and min voltages, if they are available and
|
|
|
|
|
different from each other. If they are the identical, displays same as
|
|
|
|
|
\fB\-xxm\fR voltage report. Use \fB\-ma\fR to always see them.
|
|
|
|
|
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
.TP
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
.B \-xxx \-N\fR
|
|
|
|
|
\- Adds, if present, serial number.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
\- Adds, if present, PCI/USB class ID.
|
|
|
|
|
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-xxx \-R\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- md\-raid: Adds system mdraid support types (kernel support, read ahead,
|
|
|
|
|
RAID events)
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\- zfs\-raid: Adds portion allocated (used) by RAID array/device.
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
|
New version, new man. Changes, bug fixes, enhancements! Don't delay!
Bugs:
1. A real bug, the detection for true path of /dev/root had a mistake in it and
would only have worked in half the cases. This was an easy fix, but a significant
but since it also would lead to the actual root / partition showing in Unmounted.
2. Related to the item Fixes-2, if two USB networking devices were attached,
the second one's bus and chip ID would go on the wrong line of data if -n or -i
option were used. Since that would be the line belonging to the one above,
that obviously was weird and wrong.
3. NEW: latest kernel can show hwmon data in sensors, for example from wifi chip.
This broke CPU temp detection and showed way too high cpu temp, so this fix is
fairly important since new kernels may have this new sensors hwmon syntax.
4. Sensors: IPMI alternate syntax found, also case with no data in expected columns,
just N/A, so now the ipmi sensor logic skips all lines with non numeric values in
the values column. This is what it should have done all along, it was trusting
that values would always exist for the field names it looks for.
Fixes:
1. ARM networking fix. ARM devices like rasberry pi that use usb bus for networking
showed the no data message even though usb networking was right below it. This is
corrected, and now that only shows if both main and usb networking failed for ARM.
2. Big repo fix: while testing distro and Trinity live cds, I discovered that apt is
sometimes used with rpms, which made PCLinuxOS and ALT-Linux Repos item show the
apt files but no data since the pattern was looking for start with deb. Added rpm
to pattern, so all distros that use apt running rpms should now 'just work'.
3. Fixed more distro id things, PCLinuxOS should now show its full distro string.
4. Debugger: Filtered out more blocks of /proc, that data is bloated and messy, found
another case where it collected a vast amount of junk system data from zfs in that
case, just blocked the entire range. I had no idea /proc had so much junk data in it!
5. As noted above, IPMI, yet another alternate syntax for field names. My hope that
IPMI software and sensors will be more logical and consistent than lm-sensors output
is proving to be merely wishful thinking, I think now out of 3 datasets I've gotten,
I've seen 3 variants for syntax, not to mention the ipmi-tool vs ipmi-sensors
differences. So IPMI will be like all sensors stuff, a work in progress, to
be updated with every newly discovered alternate syntax and data set.
Enhancements:
1. Disk vendors, added some, improved pattern detections for others. This feature
is getting better all the time. Thanks linuxlite hw db, easy to scan for missing
vendors in their inxi data.
2. Added more wm, budgie-wm, mwm, variants of kwin and Trinity's Twin, several others,
more refactoring of core wm/desktop code.
3. Added gpu ram and reworked memory logic for rasberry pi, which is the only SBC
I am aware of that uses that tool. Now reports the actual total, and also gpu: for
ram data, so you can tell that the gpu is using part of the total. Again, this comes
from issue #153. Also added that info to man page for -I part.
4. Added more ARM and PCI cleaners for neater and more concise ARM/PCI output.
5. Added Trinity support to Desktop section, this had at least two different detection
methods, but since the first just shows KDE original data, only the second one proved
to be Trinity specific. Happily, the full data is available, toolkit, desktop version,
and wm (Twin).
6. New -G,-A,-R -xxx feature: vendor:. Note that vendor data is very bloated and
messy so it's trimmed down substantially, using a series of filters and rules, and
thus it can contain the following: the actual vendor, like Dell, nothing, the
motherboard vendor/product for board based PCI items, or a complete vendor/product
string if it's unique. I couldn't think of a clean field name that meant:
vendor OR vendor + basic product info OR motherboard + board version OR full
product name, including vendor, so in the end, I just used vendor: but it's not
quite the right term, but nothing else seemed to work better. Testers responded
very enthusiastically about this feature so I guess the vendor: name is ok.
Changes:
1. Biggest change: Drives: HDD: total: the HDD: is now changed to: Local Storage:
This was part of issue #153 and is a good suggestion because HDD generally was used
to refer to hard disks, spinning, but with nvme, m.2, ssd, etc, that term is a bit
dated. 'Local' is because inxi does not include detected remote storage in the totals.
2. The recent --wm option which forced ps as data source for window manager detection
has been reversed, now --wm forces wmctrl and ps aux is preferred. Still falls back
to wm ctrl in case the ps test is null, this is better because I have to add the wm
data manually for each one, whereas wmctrl has an unknown set and probably variable
set of wm. Note that I reversed this because I saw several cases where wmctrl was
wrong, and reported a generic source wm instead of the real one. Since most uses are
not going to even be aware of the wm: feature as enhanced with --wm switch, this
should have no impact on users in general. Since the detected wm name needs to be
know to get assigned to wm: and wm version data, I think it will work better to
have the known variants match with the wm data values, then just fallback to
unknown ones that can get fille in over time as we find wm that people actually
use and that you can get version info on and detect.
Removed:
1. Got rid of tests for GTK compiled with version for many desktops, that test
was always wrong because it did not have any necessary relation to the actual
gtk version the desktop was built out of, and it also almost always returned no
data. Since this is an expensive and slow test, and is always going to be wrong
or empty anyway, I've removed it. My tests showed it taking about 300ms or so
to generate no data, heh.
That's the tk: feature in -S. Note I also found that gnome-shell takes
an absurdly long time to give --version info, the slowest of all such things, 300ms
again, just to show version? Someone should fix that, there's no possible reason
why it should take 300 milliseconds to give a simple version string. Note that
this returns tk: to only returning real data, which in this case means only xfce,
kde, and trinity, which are the only desktops that actually report their toolkit
data. I'll probably remove that code in the future unless I can think of some real
use for gtk version elsewhere, but it's just junk data which doesn't even work.
In the future, I will not try to emulate or guess at desktop toolkits, either they
show the data in a direct form like XFCE or Trinity or KDE do, or I won't waste
resources and execution time making bad guesses using inefficient code and logic.
QT desktops like LXQt I'm leaving in because I believe those will tend to track
more closely the QT version on the system, and the tests for QT version aren't
huge ugly hacks the way they are for GTK, so they aren't as slow or intrusive, but
those may also get removed since they almost never work either. But they are also
slowing down the -Sx process so maybe they should be removed as well, I'll think
about it. Since they only are used on LXQt and razer-qt, it probably isn't a big
deal overall.
2018-07-12 21:35:09 +00:00
|
|
|
\- Hardware RAID: Adds rev, ports, and (if available and/or relevant)
|
|
|
|
|
\fBvendor:\fR item, which shows specific vendor [product] information.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-xxx \-S\fR
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- Adds current kernel clock source, if available (Linux only).
|
|
|
|
|
|
New version, man page. Bug fixes, enhancements.
Bugs:
1. A long standing bug was finally identified and fixed. -n/-i would fail to match
a Device to the right IF in cases where they had the same chip / vendor IDs. Added
busID for non Soc type devices to fix that. I hope. This fix has been tested on a
machine that had this bug, and it is now corrected. Thanks skynet for the dataset.
2. deepin-wm was failing to get listed correctly with new fixes, this is corrected.
Fixes:
1. mate version was depending on two tools, mate-about and mate-session, which
somewhat randomly vary in which has the actual highest version number. Fix was to
run both in MATE for version, and run those through a new version compare tool.
Thanks mint/gm10 for reporting that bug.
2. -Gxx compositors: added some missing ones that were being checked for in-
correctly.
3. For distro id, fixed a glitch in the parser for files, now correctly removes
empty () with or without spaces in it.
4. Got rid of ' SOC?' part of no data for ram or slots, that also triggers in non
SOC cases, so best to not guess if I can't get it right.
Enhancements:
1. More disk vendor ID matches, also, somehow missed QEMU as vendor, thanks to
linux hardware database (linuxlite) for great samples of vendor/product strings.
2. Added a bunch of compositors, found a new source that listed a lot inxi did not
have already.
3. Added version v: for some compositors in -Gxxx.
4. New program_data() tool provides an easier to use simple program version/print
name generator, including extra level tests, to get rid of some code that repeats.
5. Found some useful QEMU virtual machines for ARM, MIPS, PPC, and SPARC, so
made initial debugging for each type, so basic working error free support is well
on its way for all 4 architectures, which was unexpected. More fine tunings to
all of them to avoid bugs, and to catch more devices, as well.
Note that QEMU images are hard to make, and they were not complete in terms of
what you would see on physical hardware, so I don't know what features will work
or not work, there may be further variants in audio/network/graphics IDs that
remain unhandled, new datasets always welcome for such platforms!
6. Found yet another desktop! Added Manokwari support, which is at this point
a reworking of gnome, but it was identifiable, minus a version number.
7. Added deepin and blankon to system base supported list, these hide their debian
roots, so I had to use the manual method to provide system base.
2018-08-28 22:23:19 +00:00
|
|
|
\- Adds, if in X, or with \fB--display\fR, bar/dock/panel/tray items
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
(\fBinfo\fR). If none found, shows nothing. Supports desktop items like
|
|
|
|
|
gnome\-panel, lxpanel, xfce4\-panel, lxqt\-panel, tint2, cairo-dock, trayer,
|
|
|
|
|
and many others.
|
New version, new man. Several bug fixes, enhancements, options.
Bugs:
1. In some cases, -S Desktop showed xfce when it wasn't xfce. This should be largely
corrected now.
2. Big bug: using lxqt-about for lxqt --version, now opens a dialog box, gui,
so removed that, and now checking lxqt-session for version info instead.
Fixes:
1. Now calling hitachi hgst drives vendor: HGST (Hitachi) to differentiate between
regular Hitachi and HGST hitachi. Added a few more disk vendors.
2. Distro base and core: added linuxlite, elementary. Some distros use:
/etc/upstream-release/lsb-release so testing for that and os-release now too.
3. Extended qt detections, may catch a few stray ones now in non kde qt
desktops.
4. Complete refactor of desktop, desktop info, wm, and -G compositor, now much
easier to extend each feature and add detections, move order around, etc.
Also moved wm to -Sxx now that I use fallback ps aux tests, which were themselves
also totally refactored and optimized. Fixed WindowMaker id, which is made more
annoying because they are the only upper/lower case program name, but in at least
debian, the actual program name is wmaker internally.
Also tightened in particular gnome-shell, which was failing to show due to too
restrictive filtering of desktop/vm repeats. Most wm do not contain the desktop
name in the string, gnome-shell does, only one I'm aware of.
5. Removed N/A from wmctrl output, which just means null, which is what we want.
6. Removed gnome-shell from info: since it will now appear in wm: if found. Added
a few -panel items to info:
Enhancements:
1. Showing type: network bridge for -N when it's type 0680, which is an odd pci
type, generally it's a network bridge, but I figured it's best to show that
explicitly to avoid confusion. This extends the 'type:' from just USB.
2. Added more window managers to wm, matchbox, flwm, fvwm2 (used to just use fvwm,
this was wrong, it's its own thing), a few others.
3. Added a few more compositors to -Gxx. kwin_x11 should be the most noticeable,
but added some more obscure ones too. This feature requires more work.
4. Extended ARM syntax to support a new one, path to /sys/device... has an extra
/soc/ in it, that is now handled, all are tested for. Confirmed working. Note that
ARM has to be confirmed fixed on a device by device basis, since there are key
syntax differences in the paths, but it will get easier the more variants that are
discovered. Added another trimmer to cut off \x00|01|02|03 special non printing
characters which show as weird jibbberish in output, for model/serial number.
5. Refactored wm, info, desktop, compositor, now all use @ps_gui, which is all that
is tested against, not the entire ps_cmd array. This drops the possible tests down
massively since the only things in ps_gui will be the actual stuff found that matches
all the patterns required for that system, not all ps items. Added marco, muffin
fixes. Was showing wm: Metacity (Marco) that is not correct, now shows marco, which
then allows to get version too.
5. -Sxxx now shows wm: version as well, which can be of use now and then.
6. --wm added to trip force using of ps data for wm, this can be useful because
I don't know all variants of wmctrl output, so that makes it easier to test.
7. Added finally support for --debug 3, which now shows timers, functions, and args
printed to screen.
8. Added qmake --version to fallback qt detection.
2018-07-08 23:30:15 +00:00
|
|
|
|
|
|
|
|
\- Adds (if present), window manager (\fBwm\fR) version number.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
2018-07-23 20:40:49 +00:00
|
|
|
\- Adds (if present), display manager (\fBdm\fR) version number.
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
|
Bugs!! Fixes! Spring cleaning!
Because these are either newly created, or newly discovered, bugs,
this release was pushed as early as possible to get them fixed asap.
BUGS:
1. Desktop: Lumina detection had a syntax error which made it not work.
This has been broken for a while.
2. Logical: if not root, and if LUKS / bcache detected, failed to load
proc_partitions, which generates error on --logical --admin since the
required components data was not loaded. This was an oversight.
3. The 3.3.02 ShellData refactor created a bug for console IRC, showed
shell, not irc client, name, and set default shell data which also
showed.
4. Console IRC tty: there was also an older bug that made -S, -G
not work consistently, and there were errors that had been missed
for many years in that logic. These should all be corrected, console
irc out of display, or in display as root, should now show tty info,
tty size in -G.
FIXES:
1. Memory: restored $bsd_type block on /proc/meminfo and force NetBSD
to use a corrected vmstat. This leaves that block of logic to correct
the NetBSD oddities in meminfo, but it may fix future isses that popup.
2. -Sxxx man page item incorrectly said XDG_VTNR was systemd/linux, it's
not, it's various things, GhostBSD has it, for example. See what you get
for believing what people say!
3. Logical: added in N/A for null maj-min in --logical report. While
bug 2 triggered those errors, there could be future cases where maj-min
are null, like BSD lvm data etc.
ENHANCEMENTS:
1. Going along with Fix 1, added '--force meminfo' in case you really want that.
2. Distro: System Base: Added TrueNAS detection.
3. Package Data: Added mport [MidnightBSD] type. That requires root to run
for some odd reason, so won't see the best output if not root.
CHANGES:
1. Moved logical to -v7 from -v8, it's stable enough now.
CODE CHANGES:
1. Moved get_tty_number and get_tty_console_irc to ShellData:tty_number
and ShellData::tty_console_irc.
ShellData::tty_number was being loaded several times, added
$loaded{'tty-number'} test, and made client{'tty-number'} to store value.
tty_console_irc changed to console_irc_tty, which is what it gets, removed
hacks and made it load once and store result in client hash.
2. Optimization: retested sub vs package::method and they run at exactly
the same time, give or take, so moving more stuff into packages to make
it easier to maintain.
2021-03-18 02:39:02 +00:00
|
|
|
\- Adds (if available, and in display), virtual terminal (\fBvt\fR) number.
|
|
|
|
|
These are the same as \fBctrl+alt+F[x]\fR numbers usually. Some systems
|
|
|
|
|
have this, some don't, it varies.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New version, new man. Fine tunings.
New features:
1. for a very few systems that have wmctrl installed, will shows -xxx wm if present
Enhancements:
1. made xorg display server and protocols show more consistently with other layout:
Display: x11 server: X.org 1.9.12 drivers: loaded: ...
if no display protocol found:
Display: server: X.org 1.9.12 drivers: loaded: ...
This brings the -G in line with the other lines, of not putting different data types
inside of parentheses as much as possible. -I still has two of these, but so far it's
not clear how to otherwise show SSH or su/sudo/login in their respective spaces.
Debugger data collector also has something I should have added ages ago, gz filename
now includes the basic 2 digit inxi version number, like 3.0 at end, so I can readily
determine the debugger inxi version, and thus avoid having to root through lots of
versions to find new stuff.
These are all largely cosmetic improvements, or debugger adjustments, except for -Sxxx
now offering wm: if present.
Also changed Desktop: name... (toolkit data) to: Desktop: name... tk: toolkit data
to be more consistent, while not adding great length to the output.
These two changes should also help export to json/xml since that puts unique key/values
back into key value pairs, not merging two together.
2018-04-12 20:23:46 +00:00
|
|
|
.TP
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.B \-xxx \-w \fR, \fB\-W\fR
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
\- Adds location (city state country), observation altitude (if available),
|
2019-02-08 04:52:41 +00:00
|
|
|
weather observation time (if available), sunset/sunrise (if available).
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.SH ADMIN EXTRA DATA OPTIONS
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
These options are triggered with \fB\-\-admin\fR or \fB\-a\fR. Admin options
|
|
|
|
|
are advanced output options, and are more technical, and mostly of interest to
|
|
|
|
|
system administrators or other machine admins.
|
Bugs:
1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic.
Fixes:
1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error)
2. Preventitive, was not using '-' quite correctly in all regex ranges.
3. Had wrong desktop string listed in Unity
4. Reordered Family/Drive model in usb drive reports, it's to make it
more obvious what is what.
5. Adjusted indexing of splits to get better results in corner cases.
6. Fixed some numbering issues.
7. Added trimming n1 from nvme0 type names for nvme, this corrects some
issues users were having.
8. Fixed a division by 0 error in smartctl data grabber.
9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0.
10. Another Perl fix, int() only wants to get numeric values sent to it,
I'd assumed a different behavior, non numerics get converted to 0, but that's
not how Perl sees things. Things like this, by the way, are why Perl is so
absurdly fast.
Enhancements:
1. More disk vendors. The list will never be complete!! We have found eternal
churn!! Thanks to linux lite hardware database as always.
2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced
drive information (with -a). See man and help for details. Will show failing drives,
etc. Lots of info can be available, but sometimes data is not in smartctl db,
so inxi can't find it, that's not an inxi bug, it's just how it is.
3. Made hours on more human readable, into days/hours, for -a smartctl disk
report.
4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out.
Note that advanced debugger outputs can change or vary depending on what is being
worked on so don't in general rely on these always being around. But they do
tend to say stuck in place once I add them.
5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it,
if not, you'll never know it's there.
6. By request from some forum issue thread: made --host only be shown onif not
--filter or not --host. This makes -z remove hostname, but retains ability to
do absolute overrides. Hostname should have always been filtered out like that,
it was an oversight. I think that was Manjaro who asked that, but I forget.
Note that this change, as usual, will not alter expected behaviors if users
have config item for hostname set.
7. Added support for picom compositor, thanks user codebling for that, I think
that's compiz fork, the real branch that is that is being developed.
2020-03-15 06:15:16 +00:00
|
|
|
|
|
|
|
|
The \fB\-\-admin\fR option sets \fB\-xxx\fR, and only has to be used once.
|
|
|
|
|
It will trigger the following features:
|
|
|
|
|
|
Bug fixes!!! New Features!! Why wait!!!
Bugs:
1. Issue #220 on github: inxi misidentified XFCE as Gnome. This was a kind of core
issue, and pointed to some logic that needed updating, and some inadequate
assumptions made, and some too loose cascade of tests. Hopefully now xfce will
almost never get misidentified, and the other primary desktops ID'ed either from
$ENV or from xrop -root will be slightly more accurately identified as well.
Note that this fix creates a possibility for obscure misconfigured desktops to
be ID'ed wrong, but in this case, that will be technically a bug for them, but
with the new fixes, that situation will be cleaner to handle internally in the
desktop ID logic.
Also tightened the final Gnome fallback detection to not trigger a possible
false positive, it was testing for ^_GNOME but that is not adequate, because
some gnome programs will trigger these values in xprop -root even if GNOME
is not running. Should be safer now, hopefully no new bugs will be triggered
by these changes.
Fixes:
1. Missed an indentation level for -y1, gcc alt should have been indented in
one more level, now it is.
2. In disk vendors/family, didn't clean items starting with '/', this is
now corrected. Yes, some do, don't ask me why. Might be cases like:
Crucial/Micron maybe, where the first ID is grabbed, not sure.
Enhancements:
1. New Disk vendors, vendor IDs!!! The list never ends!!! We've finally found
infinity, and it is the unceasing wave of tiny and not so tiny disks and their
Ids.
2. New feature: for -Aa, -Na/-na/-ia, -Ga, now will add the modules the kernel
could support if they were available on the Device-x lines of those items.
This was made an -a option because it really makes no sense, if it's a regular
option, users might think that for example an nvidia card had a nouveua driver
when it didn't, when in fact, all the kernel is saying is that it knows those
listed modules 'couid' be used or present. This corresponds to the Display:
item in -Ga, that lists 'alternate:' drivers that Xorg knows about that could
likewise be used, if they were on the system.
In other words these are --admin options because otherwise users might get confused,
so this is one where you want to know the man explanation before you ask for it.
It is useful however if you're not sure what your choices are for kernel modules.
When the alternate driver is the same as the active driver, or if none is found,
it does not show the alternate: item to avoid spamming.
2020-07-27 02:22:59 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-A\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds, if present, possible \fBalternate:\fR kernel modules capable of
|
|
|
|
|
driving each \fBDevice\-x\fR (not including the current \fBdriver:\fR). If no
|
|
|
|
|
non\-driver modules found, shows nothing. NOTE: just because it lists a module
|
|
|
|
|
does NOT mean it is available in the system, it's just something the kernel
|
|
|
|
|
knows could possibly be used instead.
|
Bug fixes!!! New Features!! Why wait!!!
Bugs:
1. Issue #220 on github: inxi misidentified XFCE as Gnome. This was a kind of core
issue, and pointed to some logic that needed updating, and some inadequate
assumptions made, and some too loose cascade of tests. Hopefully now xfce will
almost never get misidentified, and the other primary desktops ID'ed either from
$ENV or from xrop -root will be slightly more accurately identified as well.
Note that this fix creates a possibility for obscure misconfigured desktops to
be ID'ed wrong, but in this case, that will be technically a bug for them, but
with the new fixes, that situation will be cleaner to handle internally in the
desktop ID logic.
Also tightened the final Gnome fallback detection to not trigger a possible
false positive, it was testing for ^_GNOME but that is not adequate, because
some gnome programs will trigger these values in xprop -root even if GNOME
is not running. Should be safer now, hopefully no new bugs will be triggered
by these changes.
Fixes:
1. Missed an indentation level for -y1, gcc alt should have been indented in
one more level, now it is.
2. In disk vendors/family, didn't clean items starting with '/', this is
now corrected. Yes, some do, don't ask me why. Might be cases like:
Crucial/Micron maybe, where the first ID is grabbed, not sure.
Enhancements:
1. New Disk vendors, vendor IDs!!! The list never ends!!! We've finally found
infinity, and it is the unceasing wave of tiny and not so tiny disks and their
Ids.
2. New feature: for -Aa, -Na/-na/-ia, -Ga, now will add the modules the kernel
could support if they were available on the Device-x lines of those items.
This was made an -a option because it really makes no sense, if it's a regular
option, users might think that for example an nvidia card had a nouveua driver
when it didn't, when in fact, all the kernel is saying is that it knows those
listed modules 'couid' be used or present. This corresponds to the Display:
item in -Ga, that lists 'alternate:' drivers that Xorg knows about that could
likewise be used, if they were on the system.
In other words these are --admin options because otherwise users might get confused,
so this is one where you want to know the man explanation before you ask for it.
It is useful however if you're not sure what your choices are for kernel modules.
When the alternate driver is the same as the active driver, or if none is found,
it does not show the alternate: item to avoid spamming.
2020-07-27 02:22:59 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe generation, and, if different than running PCIe generation, speed
|
|
|
|
|
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
|
|
|
|
|
shown).
|
|
|
|
|
|
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 21:48:52 +00:00
|
|
|
\- Adds list of detected audio server tools (\fBtools: [tools]\fR) to API/Server
|
|
|
|
|
lines, like alsamixer, jack_control, pactl, pavuctl, pw-cli, sndioctl, etc.
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB mode (Linux only).
|
|
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.TP
|
2018-09-08 00:03:27 +00:00
|
|
|
.B \-a \-C\fR
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
.br
|
|
|
|
|
\- Adds CPU generation, process node, and built years, if detected. For Intel,
|
|
|
|
|
only will show if Core generation, otherwise the arch value is enough. For AMD,
|
|
|
|
|
only shows Zen generation.
|
|
|
|
|
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- Adds microarchitecture \fBlevel:\fR (v1,v2,v3,v4) (64 bit Intel/AMD CPUs
|
|
|
|
|
only). This information is used for setting compile time optimization switches
|
|
|
|
|
in for example GCC. These levels were introduced in 2020.
|
|
|
|
|
|
|
|
|
|
Because this a CPU flag based test, and these levels when > 2 are not always
|
|
|
|
|
100% based on exposed CPU flags (eg OSXSAVE), for > v2, adds \fBnote: check\fR.
|
|
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
\- Adds CPU family, model\-id, and stepping (replaces \fBrev\fR of \fB\-Cx\fR).
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Format is \fBhexadecimal (decimal)\fR if greater than 9, otherwise
|
|
|
|
|
\fBhexadecimal\fR.
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
\- Adds CPU microcode. Format is \fBhexadecimal\fR.
|
New version, new man. Big bug fix, new features.
Bugs:
1. Finally tracked down and solved the Xorg drivers bug which was caused by
Xorg checking its list of defaults 2 times, not 1, which resulted in failed
status on second try since it was already loaded. Secondary bug was found that
resulted in failing to show the failed, and only showing unloaded, which was also
wrong. This finally fixes issue #134 item 5. Thanks Mint users for the help on
that one.
2. Small bug in Openbox version detection, typo.
3. fixed a small glitch in the dm: detection that on systems where /var/run
exists but is not linked to /run, the dm would fail to get detected.
Fixes:
1. Xfce when defaulting to no version found goes to 4, this is a bad idea, it's
better to not show any version, since xfcie could one day be 5.
2. Fixed Blackbox fallback detection, there were cases where Blackpox not found
in xprop -root, now it falls back to ps aux detection.
3. For wm: tested all known variants, added support for things like Mutter (Marco)
syntax. Note that bunsenlab uses XDG_CURRENT_DESKTOP=XFCE to work around some
glitches, but it's actually Openbox. If run as root, it will show openbox correctly,
otherwise -Sxxx will show wm: openbox, but that's due to bunsenlabs choices there.
4. Rewrote a lot of DistroData to handle more dynamic testing of values, it's sad
that at almost 2020 we are still stumbling around trying to find a consistent way
to identify distros, and derived distros.
5. Added more debugger data collectors in the logging, some data was not
being tracked well during log process which made debugging harder.
Enhancements:
1. New feature, -Gxx now shows for Xorg drivers alternate: which are drivers that
Xorg auto checks but which are not installed. Those were ignored in the past. This
can be useful to see for example that there are other driver install options
available. Thanks gm10 for that suggestion.
2. Tested and added the following explicit handlers for Distros: and base: in
some cases:
grml, peppermint, kali, siduction, aptosid, arco, manjaro, chakra, antergos,
bunsenlabs, and a few others. These are a pain to add and test, basically I have
to boot a live cd of each one, then test the files and ID methods, but the ID
methods must also be as dynamic as possible because you never know when a distro
is going to change how they use os-release vs issue vs lsb-release vs <name>-release.
I would have tested a few more but their livecds failed to properly run on vbox.
3. Added a few more disk vendor IDs.
4. Added some more programs to debugger data collector for future feature vdpau, but
that needs more data because we don't really know the variants for example for
dual card systems.
5. Man page: changed extra options to use only one option name per list of options
for that feature, each separe item is started as a new paragraph with -
This makes it a bit more consistent and maybe slightly easier to read the man.
Added -Gxx item, updated -Sx item.
2018-07-03 21:36:15 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds socket type (for motherboard CPU socket, if available). If results
|
|
|
|
|
doubtful will list two socket types and \fBnote: check\fR. Requires
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
doas/sudo/root and \fBdmidecode\fR. The item in parentheses may simply be a
|
|
|
|
|
different syntax for the same socket, but in general, check this before trusting
|
|
|
|
|
it.
|
|
|
|
|
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
Sample: \fBsocket: 775 (478) note: check\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
Sample: \fBsocket: AM4\fR
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- Adds DMI CPU base and boost/turbo speeds. Requires doas/sudo/root and
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBdmidecode\fR. In some cases, like with overclocking or 'turbo' or 'boost'
|
|
|
|
|
modes, voltage and external clock speeds may be increased, or short term limits
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
raised on max CPU speeds. These are often not reflected in /sys based CPU
|
|
|
|
|
\fBmin/max:\fR speed results, but often are using this source.
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
|
|
|
|
|
Samples:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.br
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
CPU not overclocked, with boost, like Ryzen:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.nf
|
|
|
|
|
\fBSpeed (MHz):
|
|
|
|
|
avg: 2861
|
|
|
|
|
high: 3250
|
|
|
|
|
min/max: 1550/3400
|
|
|
|
|
boost: enabled
|
|
|
|
|
base/boost: 3400/3900\fR
|
|
|
|
|
.fi
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
Overclocked 2900 MHz CPU, with no boost available:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.nf
|
|
|
|
|
\fBSpeed (MHz):
|
|
|
|
|
avg: 2345
|
|
|
|
|
high: 2900
|
|
|
|
|
min/max: 800/2900
|
|
|
|
|
base/boost: 3350/3000\fR
|
|
|
|
|
.fi
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
Overclocked 3000 MHz CPU, with boosted max speed:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.nf
|
|
|
|
|
\fBSpeed (MHz):
|
|
|
|
|
avg: 3260
|
|
|
|
|
high: 4190
|
|
|
|
|
min/max: 1200/3001
|
|
|
|
|
base/boost: 3000/4000\fR
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
.fi
|
|
|
|
|
|
|
|
|
|
Note that these numbers can be confusing, but basically, the \fBbase\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
number is the actual normal top speed the CPU runs at without boost mode, and
|
|
|
|
|
the \fBboost\fR number is the max speed the CPU reports itself able to run at.
|
|
|
|
|
The actual max speed may be higher than either value, or lower. The \fBboost\fR
|
|
|
|
|
number appears to be hard\-coded into the CPU DMI data, and does not seem to
|
|
|
|
|
reflect actual max speeds that overclocking or other combinations of speed
|
|
|
|
|
boosters can enable, as you can see from the example where the CPU is running
|
|
|
|
|
at a speed faster than the min/max or base/boost values.
|
New inxi, man. New information types, fixes, man updates.
Bugs:
No bugs of any importance fixed or found!!
Fixes:
1. Tiny fix, didn't use partition/slice assignment in help menu. BSD
interest only since default partition is standard for Linux.
Enhancements:
1. Disc Vendors: added a large number of possible disk vendors, without having
actual detection data available for all of them, using a different source.
Also added, as usual, more disc vendor IDs from linux-lite hardware database,
always ready with more vendors!
2. Added groovy gorilla ID for ubuntu
3. Very nice usability change, mostly for support people, now if -y without
an integer is supplied, it will assign default column width of 80, which
is what you usually want for forums or issue reports, otherwise the output
can wrap outside the post or issue report, which is hard to read. Hopefully
support people will catch onto this one.
4. This closes issue #217 - Adds dmidecode based extra data:
-xxx - shows CPU voltage and external clock speeds
-a - shows CPU socket type and base/boost: speed items. These are --admin
options because neither is particularly reliable, sometimes they are right,
sometimes they aren't, as usual with dmi data. As far as tests show, base
speed, what dmidecode misleadingly calls 'Current Speed', which it isn't,
is the actual normal non throttled speed of the CPU / motherboard setup.
boost is what dmidecode calls 'Max Speed', which it also isn't, though
sometimes it is, as with AMD cpus with boost, and no overclocking. With
overclocking, sometimes base will be higher, sometimes the actual real
current cpu speeds will be higher than all the max/boost values.
Motherboard CPU socket type is likewise randomly correct, incorrect, empty,
misleading, depending on the age and type of the system, and the CPU
vendor. It appears that in general, AMD CPUs will be more or less right
if they have this data, and Intel CPUs will sometimes be right, sometimes
not, or empty. For > 1 CPU systems, the data is much less reliable.
2020-05-31 21:41:20 +00:00
|
|
|
|
|
|
|
|
Note that the normal \fBmin/max:\fR speeds do NOT show actual overclocked OR
|
|
|
|
|
boost/turbo mode speeds, and appear to be hard\-coded values, not dynamic real
|
|
|
|
|
values. The \fBbase/boost:\fR values are sometimes real, and sometimes not.
|
|
|
|
|
\fBbase\fR appears in general to be real.
|
|
|
|
|
|
Quick bug fix release. With as many changes as we got in 3.3.10, there were
bound to be a handful of oversights that were not caught in testing simply
because those hardware scenarios were not present in the tested systems.
Also minor feature enhancement for CPU scaling min/max speeds.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Due to the huge amount of changes, and the speed of change, while the new
code is working as intended, it's somewhat lacking in coding elegance since a
lot of it was hacked out very quickly, in near real time. This will get cleaned
up and refactored to be less redundant if it does not impact execution speed,
but is not pressing since there should be no functional difference.
--------------------------------------------------------------------------------
BUGS:
1. Tiny oversight, in single case CPU model id would fail because it was using
an undefined test from previous tests, not the right test, that is. Tripped
error on Elbrus for example.
2. Typo in battery secondary type status, created undefined value error. This
was I believe an older bug.
--------------------------------------------------------------------------------
FIXES:
1. PPC revision change broke Elbrus revision test for stepping. Added in more
tests to show stepping for elbrus revision.
2. Single core Elbrus in cpuinfo fallback mode failed to assign core multiplier
so L1 cache failed.
3. In cpuinfo fallback mode, Elbrus E2C3 cache data failed to appear, that data
in not per block in cpuinfo, but is the last block, so those tests had to run
on each block, not just the first one.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Show for -Ca scaling min/max speeds if different from CPU min/max speeds.
2. If no cpuinfo_min/max_freq speeds found, and scaling_min/max_freq found, set
overall min/max to use scaling min/max instead of cpuinfo min/max.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Cleaned up and proofread better 3.3.10 changelog, it had a lot of errors
because stuff kept changing.
--------------------------------------------------------------------------------
CODE:
1. Small code optimizations.
2021-12-17 00:17:02 +00:00
|
|
|
\- Adds frequency \fBscaling: governor:.. driver:..\fR if found/available. Also
|
|
|
|
|
adds scaling min/max speeds if different from standard CPU min/max spees (not
|
|
|
|
|
common).
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
|
|
|
|
|
\- Adds description of cache topology per cpu. Linux only.
|
|
|
|
|
|
|
|
|
|
\- Creates new \fBTopology:\fR line after the \fBInfo:\fR line. Moves cache data
|
|
|
|
|
to this line from \fBInfo:\fR line.
|
|
|
|
|
|
|
|
|
|
Topology line contains, if available and/or relevant: physical CPU count
|
|
|
|
|
(\fBcpus:\fR); per physical cpu core count (cores:\fR); threads per core, if > 1
|
|
|
|
|
(\fBtpc:\fR); how many \fBthreads:\fR (if more threads than cores); \fBdies:\fR
|
|
|
|
|
(rarely detected, but if so, if > 1); smt status (if no smt status found, shows
|
|
|
|
|
\fBN/A\fR).
|
|
|
|
|
|
|
|
|
|
If complex CPU type, like Alder lake, cores; will have a more granular breakdown
|
|
|
|
|
of how many mt (multi\-threaded) and how many st (single\-threaded) cores there
|
|
|
|
|
in the physical cpu ( \fBmt\-cores:\fR, \fBst\-cores:\fR); For complex CPU
|
|
|
|
|
types like ARM SoC devices with 2 CPU types, with different core counts and/or
|
|
|
|
|
\fBmin/max:\fR) frequencies, \fBvariant:\fR per type found, with relevant
|
2022-07-27 21:03:40 +00:00
|
|
|
differences shown, like \fBcores:\fR, \fBmin/max:\fR, etc.
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBCPU:
|
|
|
|
|
Info:
|
|
|
|
|
model: AMD EPYC 7281
|
|
|
|
|
bits: 64
|
|
|
|
|
type: MT MCP MCM SMP
|
|
|
|
|
arch: Zen
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
gen: 1
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
level: v3
|
|
|
|
|
note: check
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
process: GF 14nm
|
Bug release, replace 3.3.17 asap, most users will not experience the bug, but if
they do, inxi stops right before the -D line. Failed to do an if defined test on
an array ref that could be undefined or an array ref. That makes Perl very
unhappy!
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. AMD family F, K8 series, will need more granular treatments to get the data
to be more accurate and less generic. We got 2 IDs nailed from raw visual data
confirmations and cpuid values, which leaves many, but good start. We will chip
away (pardon the pun) at these more ambiguous IDs over time, but don't need to
get them all done instantly, just eventually. Thanks slackware person linuxdaddy
for doing really good research and actually looking at the cpu to find dates
etc.
--------------------------------------------------------------------------------
BUGS:
1. Bug, fatal, caused by internal hash/array ref refactor of 3.3.17. Thanks
alaymari github issue #271 for reporting this one.
--------------------------------------------------------------------------------
FIXES:
1. None except for code fixes to try to avoid the cause of the bug in Bugs 1.
2. Fixed nvidia eol try --gpu, it was showing backwards, with --gpu, not
without, sigh.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added slimski dm data. That's a new fork of SLiM. Also guessing that brzdm
has same version -v output: brzdm version x.xx
--------------------------------------------------------------------------------
CHANGES:
1. None
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Refactors of core docs, ongoing, but will list those next release.
--------------------------------------------------------------------------------
CODE:
1. Cleaned up some array ref handling in subs, returned as: ($var1,$var2) =
@{block_data(...)}, skipped initializing and creating scalar to hold the ref,
just use it directly for DiskItem::block_data().
2. Also switched to local ref scalar array in DiskItem::scsi_data(),
DiskItem::block_data(). Not set local array, set local array ref, to keep it
clear. Also made DriveItem::drive_speed() return straight ref, not array then
ref. Same for many other subs, switched to ref assignment so it's the same ref
all through all the sub and return.
3. Fixed a redundant return \@$data to simply assinging to @$data ref, no return
needed, in DiskItem::smartctl_data().
4. Tightened some returns of ref so that tests if good test @$ref, not $ref.
Trying to avoid more cases like issue #271.
5. Going along with array ref local/return, switched all hash refs to local hash
ref returning ref, and working local with ref. More efficient, avoids creating
new refs over and over, dugh. This made a particularly large difference in CPU
because in certain parts, new references were being created over and over, and
subs were returning like \@arr or \%hash instead of declaring to start:
my $arr = []; my $hash = {};
Then working with the data from there on as an array or hash reference, to the
same original reference, rather than creating new ones over and over, which Perl
then has to track til they expire.
2022-06-13 23:32:32 +00:00
|
|
|
built: 2017\-19
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
family:0x17 (23)
|
|
|
|
|
model\-id:1
|
|
|
|
|
stepping: 2
|
|
|
|
|
microcode: 0x8001250
|
|
|
|
|
Topology:
|
|
|
|
|
cpus: 2
|
|
|
|
|
cores: 16
|
|
|
|
|
tpc: 2
|
|
|
|
|
threads: 32
|
|
|
|
|
dies: 4
|
|
|
|
|
cache:
|
|
|
|
|
L1: 2x 1.5 MiB (3 MiB)
|
|
|
|
|
desc: d\-16x32 KiB; i\-16x64 KiB
|
|
|
|
|
L2: 2x 8 MiB (16 MiB)
|
|
|
|
|
desc: 16x512 KiB
|
|
|
|
|
L3: 2x 32 MiB (64 MiB)
|
|
|
|
|
desc: 8x4 MiB
|
|
|
|
|
Speed (MHz):
|
|
|
|
|
avg: 1195
|
|
|
|
|
high: 1197
|
|
|
|
|
min/max: 1200/2100
|
|
|
|
|
boost: enabled
|
|
|
|
|
scaling:
|
2021-12-14 18:42:16 +00:00
|
|
|
driver: acpi\-cpufreq
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
governor: ondemand
|
|
|
|
|
cores:
|
|
|
|
|
1: 1195
|
|
|
|
|
2: 1196
|
|
|
|
|
....
|
2022-07-27 21:03:40 +00:00
|
|
|
bogomips: 267823\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
.fi
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds CPU Vulnerabilities (bugs) as known by your current kernel. Lists by
|
New version, man page. Fixes, enhancements, changes.
Thanks:
1. AntiX forums, for testing -C --admin, suggestions, always helpful.
Bugs:
1. Added switch to set @ps_gui, I forgot case where info block was only thing
that used ps_gui (Nitrux kde nomad latte case). This led to no info: data if
other ps_gui switches not activated. Now each block that can use it activates it.
Fixes:
1. To clarify issue #161 added help/man explanation on how to get colors in cases
where you want to preserve colors for piped or redirected output. Thanks fugo.
2. LMDE 3.0 released, slightly different system base handling, so refactored to
add Debian version, see enhancement 2. Tested on some old vm instances, improved
old system Debian system base id, but it's empirical, distro by distro, there is
no rule I can use to automatically do it, sadly.
3. 'Motherboard' sensors field name added, a few small tweaks to sensors. This
was in response to issue #159, which also raised a problem I was not really
aware of, user generated sensor config files, that can have totally random
field names. Longer term solution, start getting data from sys to pad out
lm-sensors data, or to handle cases where no lm-sensors installed.
4. Fixed kwin_11 and kwin_wayland compositor print names, I'd left out the _,
which made it look strange, like there were two compositors or something.
5. Fixed latte-dock ID, I thought the program name when running was latte, not
latte-dock. inxi checks for both now. Thanks Nitrux for exposing that in vm test.
6. Sensors: added in a small filter to motherboard temp, avoid values that are
too high, like SYSTIN: 118 C, filters out to only use < 90 C. Very unlikely a
mobo would be more than 90C unless it's a mistake or about to melt. This may
correct anoymous debugger dataset report from rakasunka.
Enhancements:
1. Added --admin to -v 8 and to --debugger 2x
2. Expanded system base to use Debian version tool, like the ubuntu one, that
lets me match version number to codename. The ubuntu one matches code names to
release dates. Added Neptune, PureOS, Sparky, Tails, to new Debian system base
handler.
3. Big enhancement: --admin -C now shows a nice report on cpu vulnerabilities,
and has a good error message if no data found. Report shows:
Vulnerabilities: Type: [e.g. meltdown] status/mitigation: text explanation.
Note: 'status' is for when no mitigation, either not applicable, or is vulnerable.
'mitigation' is when it's handled, and how. Thanks issue #160 Vascom from Fedora
for that request.
4. The never-ending saga of disk vendor IDs continues. More obscure vendors,
more matches to existing vendors. Thanks linuxlite/linux hardware database
Changes:
1. Reordered usb output, I don't know why I had Hubs and Devices use different
ordering and different -x switch priorities, that was silly, and made it hard to
read.
Now shows:
Device/Hub: bus-id-port-id[.port-id]:device-id info: [product info]
type/ports: [devices/hubs] usb: [type, speed]
-x adds drivers for devices, and usb: speed is now default for devices, same as
Hubs. Why I had those different is beyond me.
The USB ordering is now more sensible, the various components of each
matching whether hub or device.
Unfixable or Won't Fix:
1. Unable to detect Nomad desktop. As far as I can tell, Nomad is only a theme
applied to KDE Plasma, there is no program by that name detectable, only a
reference in ps aux to a theme called nomad.
2. Nitrux system base ID will not work until they correct their /etc/os-release file.
3. Tails live cd for some inexplicable reason uses non standard /etc/os-release
field names, which forces me to either do a custom detection just for them, or for
them to fix this bug. I opted for ignoring it, if I let each distro break standard
formats then try to work around it, the distro ID will grow to be a 1000 lines long
easily. Will file distro bug reports when I find these from now on.
Samples:
This shows the corrected, cleaned up, consistent usb output:
inxi -y80 --usb
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID usb: 1.1
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse usb: 1.1
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse usb: 1.1
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
usb: 2.0
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network usb: 2.0
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
inxi -y80 --usb -xxxz
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
chip ID: 1d6b:0002
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1 chip ID: 03eb:0902
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID driver: cm109,snd-usb-audio interfaces: 4 usb: 1.1
chip ID: 0d8c:000e
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse driver: usbhid,wacom
interfaces: 1 usb: 1.1 chip ID: 056a:0011
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse
driver: hid-generic,usbhid interfaces: 2 usb: 1.1 chip ID: 0d3d:0001
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
driver: N/A interfaces: 1 usb: 2.0 chip ID: 04a9:1909
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network
driver: asix interfaces: 1 usb: 2.0 chip ID: 05ac:1402 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
chip ID: 1d6b:0003
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
chip ID: 1d6b:0002
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
chip ID: 1d6b:0003
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
chip ID: 1d6b:0002
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
chip ID: 1d6b:0003
2018-09-07 20:58:55 +00:00
|
|
|
\fBType: ... (status|mitigation): ....\fR for systems that support this feature
|
|
|
|
|
(Linux kernel 4.14 or newer, or patched older kernels).
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
.TP
|
2019-05-01 02:06:19 +00:00
|
|
|
.B \-a \-d\fR,\fB\-a \-D\fR
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
\- Adds logical and physical block size in bytes.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Using \fBsmartctl\fR (requires doas/sudo/root privileges).
|
Bugs:
1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic.
Fixes:
1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error)
2. Preventitive, was not using '-' quite correctly in all regex ranges.
3. Had wrong desktop string listed in Unity
4. Reordered Family/Drive model in usb drive reports, it's to make it
more obvious what is what.
5. Adjusted indexing of splits to get better results in corner cases.
6. Fixed some numbering issues.
7. Added trimming n1 from nvme0 type names for nvme, this corrects some
issues users were having.
8. Fixed a division by 0 error in smartctl data grabber.
9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0.
10. Another Perl fix, int() only wants to get numeric values sent to it,
I'd assumed a different behavior, non numerics get converted to 0, but that's
not how Perl sees things. Things like this, by the way, are why Perl is so
absurdly fast.
Enhancements:
1. More disk vendors. The list will never be complete!! We have found eternal
churn!! Thanks to linux lite hardware database as always.
2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced
drive information (with -a). See man and help for details. Will show failing drives,
etc. Lots of info can be available, but sometimes data is not in smartctl db,
so inxi can't find it, that's not an inxi bug, it's just how it is.
3. Made hours on more human readable, into days/hours, for -a smartctl disk
report.
4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out.
Note that advanced debugger outputs can change or vary depending on what is being
worked on so don't in general rely on these always being around. But they do
tend to say stuck in place once I add them.
5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it,
if not, you'll never know it's there.
6. By request from some forum issue thread: made --host only be shown onif not
--filter or not --host. This makes -z remove hostname, but retains ability to
do absolute overrides. Hostname should have always been filtered out like that,
it was an oversight. I think that was Manjaro who asked that, but I forget.
Note that this change, as usual, will not alter expected behaviors if users
have config item for hostname set.
7. Added support for picom compositor, thanks user codebling for that, I think
that's compiz fork, the real branch that is that is being developed.
2020-03-15 06:15:16 +00:00
|
|
|
|
|
|
|
|
\- Adds device model family, like \fBCaviar Black\fR, if available.
|
|
|
|
|
|
|
|
|
|
\- Adds SATA type (eg 1.0, 2.6, 3.0) if a SATA device.
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
\- Adds device kernel major:minor number (Linux only).
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds SMART report line: status, enabled/disabled, health, powered on, cycles,
|
|
|
|
|
and some error cases if out of range values. Note that for Pre\-fail items, it
|
|
|
|
|
will show the VALUE and THRESHOLD numbers. It will also fall back for unknown
|
|
|
|
|
attributes that are or have been failing and print out the Attribute name,
|
|
|
|
|
value, threshold, and failing message. This way even for unhandled Attribute
|
|
|
|
|
names, you should get a solid report for full failure cases. Other cases may
|
|
|
|
|
show if inxi believes that the item may be approaching failure. This is a guess
|
|
|
|
|
so make sure to check the drive and smartctl full output to verify before taking
|
|
|
|
|
any further action.
|
Bugs:
1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic.
Fixes:
1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error)
2. Preventitive, was not using '-' quite correctly in all regex ranges.
3. Had wrong desktop string listed in Unity
4. Reordered Family/Drive model in usb drive reports, it's to make it
more obvious what is what.
5. Adjusted indexing of splits to get better results in corner cases.
6. Fixed some numbering issues.
7. Added trimming n1 from nvme0 type names for nvme, this corrects some
issues users were having.
8. Fixed a division by 0 error in smartctl data grabber.
9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0.
10. Another Perl fix, int() only wants to get numeric values sent to it,
I'd assumed a different behavior, non numerics get converted to 0, but that's
not how Perl sees things. Things like this, by the way, are why Perl is so
absurdly fast.
Enhancements:
1. More disk vendors. The list will never be complete!! We have found eternal
churn!! Thanks to linux lite hardware database as always.
2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced
drive information (with -a). See man and help for details. Will show failing drives,
etc. Lots of info can be available, but sometimes data is not in smartctl db,
so inxi can't find it, that's not an inxi bug, it's just how it is.
3. Made hours on more human readable, into days/hours, for -a smartctl disk
report.
4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out.
Note that advanced debugger outputs can change or vary depending on what is being
worked on so don't in general rely on these always being around. But they do
tend to say stuck in place once I add them.
5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it,
if not, you'll never know it's there.
6. By request from some forum issue thread: made --host only be shown onif not
--filter or not --host. This makes -z remove hostname, but retains ability to
do absolute overrides. Hostname should have always been filtered out like that,
it was an oversight. I think that was Manjaro who asked that, but I forget.
Note that this change, as usual, will not alter expected behaviors if users
have config item for hostname set.
7. Added support for picom compositor, thanks user codebling for that, I think
that's compiz fork, the real branch that is that is being developed.
2020-03-15 06:15:16 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds, for USB or other external drives, actual model name/serial if
|
|
|
|
|
available, and different from enclosure model/serial, and corrects block sizes
|
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 18:59:56 +00:00
|
|
|
if necessary.
|
|
|
|
|
|
|
|
|
|
\- Adds for USB drives USB mode (Linux only).
|
|
|
|
|
|
|
|
|
|
\- Adds in drive temperature for some drives as well, and other useful data.
|
Bugs:
1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic.
Fixes:
1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error)
2. Preventitive, was not using '-' quite correctly in all regex ranges.
3. Had wrong desktop string listed in Unity
4. Reordered Family/Drive model in usb drive reports, it's to make it
more obvious what is what.
5. Adjusted indexing of splits to get better results in corner cases.
6. Fixed some numbering issues.
7. Added trimming n1 from nvme0 type names for nvme, this corrects some
issues users were having.
8. Fixed a division by 0 error in smartctl data grabber.
9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0.
10. Another Perl fix, int() only wants to get numeric values sent to it,
I'd assumed a different behavior, non numerics get converted to 0, but that's
not how Perl sees things. Things like this, by the way, are why Perl is so
absurdly fast.
Enhancements:
1. More disk vendors. The list will never be complete!! We have found eternal
churn!! Thanks to linux lite hardware database as always.
2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced
drive information (with -a). See man and help for details. Will show failing drives,
etc. Lots of info can be available, but sometimes data is not in smartctl db,
so inxi can't find it, that's not an inxi bug, it's just how it is.
3. Made hours on more human readable, into days/hours, for -a smartctl disk
report.
4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out.
Note that advanced debugger outputs can change or vary depending on what is being
worked on so don't in general rely on these always being around. But they do
tend to say stuck in place once I add them.
5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it,
if not, you'll never know it's there.
6. By request from some forum issue thread: made --host only be shown onif not
--filter or not --host. This makes -z remove hostname, but retains ability to
do absolute overrides. Hostname should have always been filtered out like that,
it was an oversight. I think that was Manjaro who asked that, but I forget.
Note that this change, as usual, will not alter expected behaviors if users
have config item for hostname set.
7. Added support for picom compositor, thanks user codebling for that, I think
that's compiz fork, the real branch that is that is being developed.
2020-03-15 06:15:16 +00:00
|
|
|
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-E\fR (\fB\-\-bluetooth\fR)
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- Adds (\fBhciconfig\fR only) extra line to \fBReport:\fR, \fBInfo:\fR.
|
|
|
|
|
Includes, if available, ACL MTU, SCO MTU, Link policy, Link mode,
|
|
|
|
|
and Service Classes.
|
Bug fixes!! New Feature!! Edits, cleanups!!
Bugs:
1. Small bug, wrong regex would make mdraid unused report never show.
Was looking for ^used, not ^unused. No idea how that happened, but it's fixed.
2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset,
inxi had a bunch of bugs around that. I'd assumed active and inactive would have
roughly the same syntax, but they don't. This is now corrected. Thanks Solus user
for giving me the required data. This case when not corrected resulted in a
spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid.
3. A bug that probably never impacted anyone, but in SMART the matching rules
failed to match field name Size[s]? in the logical/physical block sizes.
However, those were already coming in from I believe pre-existing /sys data
for the drives but now it's fixed anyway. I had not realized that smartctl
made it plural when logical/physical were different, and singular when
they were the same.
Fixes:
1. Going along with bug 2, fixed some other admin/non admin report glitches.
Made patterns more aggressively matching, whitelist based to avoid the types
of syntax issues that caused bug 2.
2. Added 'faulty' type to mdraid matches, that had not been handled.
3. Found even more of those pesky 'card' references in help and man page,
replaced all of them with 'device[s]'.
4. Subtle fix, for debugger data collectors, added -y1 support, which can
be useful at times.
Enhancements:
1. In USB data grabber, added fallback case for unspecified type cases, now
uses a simple name/driver string test to determine if it's graphics, audio,
or bluetooth. This was mainly to make sure bluetooth usb devices get caught.
2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report.
Requires for the 'Report:' part hciconfig, which most all distros still have
in their repos. With -a, shows an additional Info: line that has more obscure
bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes.
This closes the ancient, venerable issue #79, filed by mikaela so many years
ago. Better late than never!! However, features like this were really difficult
in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess
we'll slowly whittle away at these things when the mood, and global pandemic
lockdowns, make that seem like a good idea...
Includes a small lookup table to match LMP number to Bluetooth version (bt-v:),
hopefully that's a correct way to determine bluetooth version, there was some
ambiguity about that.
-x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N
devices, adding Chip IDs, Bus IDs, version info, and so on.
Since this bluetooth report does not require root and is an upper case option,
it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth
shows only if data is found. With -v7 or -R or -E, always shows, including
no data found message.
Includes a fallback report Report-ID: case where for some reason, inxi could
not match the HCI ID with the device. That's similar to IF-ID in -n, which
does the same when some of the IFs could not be matched to a specific device.
3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is
actually useful for many cases of trying to figure out what devices are,
though most users would not know what to do with that information, but that's
why it's an -xxx option!
4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!!
The cornucopia flows its endless bounty over the grateful data collector, and,
hopefully, inxi users!! Thanks as always, linux-lite hardware database, and
linux-lite users who really seem set on the impossible project of obtaining
all the disks/vendors known to man.
Changes:
1. Small change in wording for mdraid report:
'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner
and much more precise.
2021-01-29 04:02:42 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe generation, and, if different than running PCIe generation, speed
|
|
|
|
|
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
|
|
|
|
|
shown. Bluetooth PCIe rare).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB mode (Linux only).
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- Adds, if present, bluetooth \fBstatus:\fR discoverable, active discoverable,
|
|
|
|
|
and pairing items.
|
|
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-G\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds, if present, possible \fBalternate:\fR kernel modules capable of driving
|
|
|
|
|
each \fBDevice\-x\fR (not including the current \fBloaded:\fR). If no
|
|
|
|
|
non\-driver modules found, shows nothing. NOTE: just because it lists a module
|
|
|
|
|
does NOT mean it is available in the system, it's just something the kernel
|
|
|
|
|
knows could possibly be used instead.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
\- Adds (AMD/Intel/Nvidia, if available) \fBprocess: [node] built: [years]\fR
|
2022-07-27 21:03:40 +00:00
|
|
|
to \fBarch:\fR item.
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
|
|
|
|
|
\- Adds (if Linux and Nvidia device) non\-free support information (if
|
|
|
|
|
available). This can be useful for forum support people to determine if the card
|
|
|
|
|
supports current active legacy Nvidia driver branches, or if the card nonfree
|
|
|
|
|
driver is EOL or active. Note that if card is current, shows basic series and
|
|
|
|
|
status.
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
|
|
|
|
|
Includes extended non free Nvidia legacy informatin (Linux and Nvidia only), and
|
|
|
|
|
\fBarch:\fR reports (AMD/Intel/Nvidia). Useful to help diagnose driver support
|
|
|
|
|
issues, shows extra data that can help diagnose/debug. Adds \fBcode:\fR item if
|
|
|
|
|
found and not the same as \fBarch:\fR.
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB mode (Linux only).
|
|
|
|
|
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
.nf
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\fBinxi \-Gaz
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
Graphics:
|
|
|
|
|
Device\-1: NVIDIA NV34 [GeForce FX 5200] driver: nouveau v: kernel
|
2022-07-27 21:10:52 +00:00
|
|
|
non\-free: 173.14.xx status: legacy (EOL) last: kernel: 3.12 xorg: 1.15
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
release: 173.14.39 arch: Rankine code: NV3x process: 130\-150nm
|
2022-07-27 21:10:52 +00:00
|
|
|
built: 2003\-05 ports: active: VGA\-1 empty: DVI\-I\-1,TV\-1
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
bus\-ID: 01:00.0 chip\-ID: 10de:0322 class\-ID: 0300
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
Display: x11 server: X.Org v: 21.1.3 driver: X: loaded: nouveau
|
|
|
|
|
unloaded: fbdev,modesetting,vesa alternate: nv,nvidia gpu: nouveau
|
|
|
|
|
display\-ID: :0 screens: 1\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
2022-07-27 21:03:40 +00:00
|
|
|
With \fB\-y1\fR:
|
|
|
|
|
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
.nf
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\fBinxi \-Gaz \-y1
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
Graphics:
|
|
|
|
|
Device\-1: NVIDIA NV34 [GeForce FX 5200]
|
|
|
|
|
driver: nouveau
|
|
|
|
|
v: kernel
|
|
|
|
|
non\-free:
|
|
|
|
|
series: 173.14.xx
|
|
|
|
|
status: legacy (EOL)
|
|
|
|
|
last:
|
|
|
|
|
kernel: 3.12
|
|
|
|
|
xorg: 1.15
|
|
|
|
|
release: 173.14.39
|
|
|
|
|
arch: Rankine
|
|
|
|
|
code: NV3x
|
|
|
|
|
process: 130\-150nm
|
|
|
|
|
built: 2003\-05
|
|
|
|
|
ports:
|
|
|
|
|
active: VGA\-1
|
|
|
|
|
empty: DVI\-I\-1,TV\-1
|
|
|
|
|
bus\-ID: 01:00.0
|
|
|
|
|
chip\-ID: 10de:0322
|
2022-07-27 21:03:40 +00:00
|
|
|
class\-ID: 0300\fR
|
A good bug fix, and several very good indentation fixes that had always been
around, and some of them known. More fine tuning of CPU process/built data. Bit
by bit it's getting filled out.
Thanks again mrmazda for all the suggestions and watchful eyes.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. CPU built, process are not perfect and complete and always right. Like life,
it's not perfect, but it is ok. Help complete the feature if it bothers you.
2. Intel Raptor Lake and related APUs are trickling out, but I have not found
cpuid data for the cpu, or generation data for the apu. Was hoping to squeeze
that into 3.3.20, but looks like it will have to go into 3.3.21 or later.
--------------------------------------------------------------------------------
BUGS:
1. MrMazda pointed this out, the printer was not correctly indenting long values
in specific cases, not adding indentation level 1 when the key: value pair was
not the last item on the logical line. Subtle, but could hit Device, OpenGL, and
a few other cases.
2. When SMT is disabled, cpu speed from /sys can return <unknown>, which is a
string, not the numeric value inxi expected. This trips multipe errors when
speed cleaner is used. Thanks issue #273 reporter iamc for this one. My guess is
all during all cpu testing, none of us thought to disable smt to see what would
happen.
--------------------------------------------------------------------------------
FIXES:
1. On disk vendors, Initio isn't a vendor, it's either a misconfigured ide hdd,
slave/master wrong, or bad usb controller. Initio is a default controller, not a
vendor. Added pre-filter in disk_vendor() to remove that string if it appears.
2. Going along with bug 1, finally fixed long standing weakness with long value
wrapping, now continues to build line until it's done, and does not force a new
line after the last long value item.
3. Another glitch where last key: value pair was less than working width, but
total width was greater, was not wrapping correctly.
4. Saw a corner case Intel Core name: Core i7-1165G7 which did not use the
expected intel (core number)(3 digits), modified to look for 3 digits after core
numer OR 2 digits + letter + digit.
5. Added 'tar' installed test for debugger, found cases in actual distros that
shipped without it in their minimal installs. Times sure have changed!
6. Another Centos type change, amazingly, this was shipped without lspci as
well! No idea what went into the install ISO if this stuff didn't include the
most elementary Linux tools. Added lspci missing error if linux and not risc and
no pci_tool detected. I have to admit this is really surprising to me, I mean, I
thought the entire purpose of the rhel family was to provide enterprise
solutions, but to leave out such elementary tools required by every sys admin is
very difficult to understand. This was centos 7.5. I believe Alma and Rocky 9
minimal have those basic tools, so that's an improvement, though they didn't
have tar.
7. Added a '-' between gen and gen number for Intel GPU generation output. Even
though it's documented as for example gen9.5, it looks odd to see it that way,
it's easier to read it as gen-9.5 I think.
8. Did same for AMD arch/codes, for numbered arch/codes like Rage 9, easier to
read as Rage-9.
9. Extreme corner case spotted by mrmazda, if KDE is started by TDE, inxi showed
Trinity, not KDE-Plasma as the desktop. Further, it failed to show Trinity
version, maybe because Trinity was not installed?
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. More or less completed verification of AMD cpu microarch/built/process, and
added more accurate fallback cases for stray model IDs.
* family 5h: K5, K6
* family 6h: K7
* family 7h: K8 - mostly done, needs some checks.
* family 10h: K10
* family 11h: K11 Turion X2. Note there is some uncertainy about this family
name. Built years n/a yet. Mix of K8/K10
* family 12h: K12 Fusion, K10 based, first APU type?
1b. Extended Intel cpu data a bit more as well. Thanks linuxdaddy from slackware
for the research help there.
* family 4: mostly new, fine tuned, granular
* family 5: more granular, better date/process info.
* family 6: built dates added
* family F: corrected some overly specific stuff
2. Tentative support for finit init system (fast init). Runs in /proc/1/comm,
uses initctl, which may have been revived from its upstart days, not sure. Added
potential support for nosh, linux only, don't know how to detect other bsd init
system.
3. Added amd/intel gpu product IDs.
4. Added shortcut --filter-all/--za, activates all filters: -z, --zl, --zu,
--zv. Why not?
5. Added support for dm types kdmctl and xdmctl, opensuse and maybe redhat use
the latter to start the actual dm running the desktop/wm. You want to see that
because you need to do systemctl restart xdm to restart the actual dm. Thanks
mrmazda for pointing out this one.
6. Added AlmaLinux, RockyLinux, CentosStream to system base (RHEL derived).
7. Basic Raptor Lake gpu/apu support added, with patterns to detect since few
product ids yet. Same applies to Arctic and Alchemist, which still have no
product IDs.
8. More disk vendors and disk vendor ids, never stops - the waters flow on, the
rain falls, then the sun comes out. Until one day it doesn't.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --gpu, now it works the same as -Ga, that was too granular and
nobody would use it I think. Now that the new gpu features are solid, no need
for this special feature.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated docs/inxi-values.txt, it didn't have all the --debug-xxx options
listed.
2. Split out some BSD data into docs/inxi-bsd.txt.
3. Big update on docs/inxi-init.txt, moved data to it from other files, updated
the init/service tool data.
4. Renamed init-data.txt to inxi-init.txt, renamed cpu-flags to
inxi-cpu-flags.txt to be more consistent.
5. Updated help, man for new --filter-all option.
6. Updated help and man for --gpu deprecation.
--------------------------------------------------------------------------------
CODE:
1. Moved required perl modules and system programs checks to
check_required_items() in debugger, why not? Also added an error handler for
missing required programs, this is really the only one, and only for
--debug >= 20
This is the only required program test inxi has in it I believe, really amazing
that such a core tool would be left out of an OS today.
2. Removed this redundant block of code from Network device_output() end
section, that repeated in the main get() so didn't seem to serve any purpose.
The test in get() is if n!@rows and if !%risc, same as here, so can't see any
use for it. I'm leaving this here in case that did have some use, but I don't
see it.
if (!@$rows && !%risc){
my $key = 'Message';
my $type = 'pci-card-data';
if ($pci_tool && $alerts{$pci_tool}->{'action'} eq 'permissions'){
$type = 'pci-card-data-root';
}
@$rows = ({
main::key($num++,0,1,$key) => main::message($type,'')
});
}
2022-07-27 19:02:36 +00:00
|
|
|
.fi
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds PCIe generation, and, if different than running PCIe generation, speed
|
|
|
|
|
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
|
|
|
|
|
shown).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds to Monitors \fBbuilt:\fR, \fBgamma:\fR, \fBratio:\fR (if found).
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
X.org sample (with both \fBxdpyinfo\fR and \fBxrandr\fR data available):
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.nf
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fBinxi \-aGz
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
Graphics:
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Device\-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
|
2022-07-27 21:10:52 +00:00
|
|
|
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
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
compositor: xfwm v: 4.16.1 driver: X: loaded: modesetting dri: r600
|
|
|
|
|
gpu: radeon display\-ID: :0.0 screens: 1
|
2022-07-27 21:10:52 +00:00
|
|
|
Screen\-1: 0 s-res: 2560x1024 s-dpi: 96 s\-size: 677x270mm (26.65x10.63")
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
s\-diag: 729mm (28.7")
|
2022-07-27 21:10:52 +00:00
|
|
|
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:
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
max: 1280x1024 min: 720x400
|
2022-07-27 21:10:52 +00:00
|
|
|
Monitor\-2: VGA\-1 pos: right model: Dell 1908FP serial: <filter>
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
built: 2008 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.4
|
2022-07-27 21:10:52 +00:00
|
|
|
size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4 modes:
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
max: 1280x1024 min: 720x400
|
This release fixes another very long standing bug, which I was not sure was an
inxi or a Konversation bug, which made tracking it down very difficult. Special
thanks to argonel of Konversation for helping solve this problem, or at least,
for directing my attention towards the likely cause area, and away from wrong
ideas. The bug was that inxi simply did not run in Konversation, it would exit
with error when run with /cmd or /inxi via symbolic links.
This may not seem like a huge deal to many of you, but the actual history of
inxi was directly linked to user support in mainly Konversation, so this feature
not working I have alwyas found extremely annoying, but I could never figure out
why it wasn't workiing, and didn't really know where to start until Argonel
helped narrow it down to a specific Konversation function in inxi. At which
point tracking down the real bug was fairly easy. Since testing in IRC is always
a key test point for inxi features and releases, not working in my main GUI IRC
client forced me to use CLI clients like irssi, via /exec -o inxi.
There was a secondary cause of failure, which was missing a key qdbus package,
which made figuring this one out a two step process.
So inxi is once again working in all areas, with no known significant failure
areas beyond known issues that have no current solution, or which I don't feel
like doing.
But possibly more important, a goal I have had for a while now of doing long
needed code refactors, bug fixes, without huge new code blocks or features
adding new future fixes and bugs, has been slowly happening.
This was quite important, because inxi's codebase and logic is so complex and
large now that at some point, it required rest and cleanup and corrections,
without continuously adding new code and logic, which would then trigger new
fixes and bugs. In other words, the code is taking a long needed, and well
deserved, breather, to recover after huge increases in the overall LOC and
feature sets.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. No known way to detect that the system might be Wayland for the Graphics:..
API: fixes, unless Xwayland is installed if the wayland protocol detections
failed, which they often do in console. Not practical to look for all compositor
variants on system to determine if it could be Wayland if not X or Xvesa, so
that one will just be what it is, which is fine, definitely better than it was
before. Note this is only an issue if in Console, no Display. Note that if inxi
is run as root, Wayland data also usually fails, even in Display.
--------------------------------------------------------------------------------
BUGS:
1. Another corner case monitor position issue, applied fallback primary monitor
rule when a primary monitor had already been located. This is corrected via a
graphics global $b_primary which once set will disable this fallback feature.
Objectively, the fallback feature should just be removed. The test is if that
monitor is not primary, and if position is 0x0, then assume primary, without
verifying no primary had been located yet.
2. A super old bug, in current konversation, was failing to trip the konvi
detections, which then resulted in not stripping off the first two args in
@ARGV, which then resulted in bad args being passed to inxi on konvi start,
which then resulted in silent failing. Many thanks to argonel of #konversation
for the patience to help me figure out what was going on with this bug. He's
been a Konversation developer probably longer than I've been doing inxi.
Cause was very tricky and subtle, the ps aux path for konvi had changed
slightly, not the path, but the pattern, it used to be:
konversation -session [sessin id]
but it's changed to:
konversation -qwindowtitle Konversation
or just plain:
konversation as line ending.
This led to failure to find konvi running, which then made the konvi ids fail.
Also, this would not work if the qdbus-qt5 package was not installed, or other
distros might have that packaged differently. Because of these dual causes, I
was simply unable to figure out what was going on for many years. I suspect this
stopped working with KDE 5/QT 5, but I'm not sure.
3. Used wrong key names for some ZFS tests and fallbacks, those could have led
to failures though very difficult to test and verify this. Also see fix 5, which
of course also looks like a bug, acts like one, but was actually due to a new
use of /dev/disk/by-partuuid for ZFS components in Ubuntu which inxi had not
seen before.
--------------------------------------------------------------------------------
FIXES:
1. Alternate ps IDs for appimage detection (try appimagelauncher), alternate
paths for possible appimage storage locations (also try ~/.appimage/*). File
names might be *.appimage or *.AppImage, probably other variants too.
2. Going along with Change 1, made tests more granular for missing graphics API
type data. Also updated messages to be more correct and clear, in and out of
display. This corrects an issue I'd seen but never resolved, which was on
headless systems showing this message:
Message: GL data unavailable in console. Try -G --display
Now the tests are far more granular, and only show that if glxinfo is installed,
and also shows specific messages if glxinfo not installed, but X/Xorg present,
or, for Wayland, if Xwayland present. These all get their own specific messages
now, and generally will also show which API is being used, or API: N/A if
nothing is detected, as in the case of a headless system with no X, Wayland,
etc.
3. Github issue #275 on of all things Microsoft WSL environment, has a small
glitch with undefined display hz, but otherwise inxi seems to work in that
environment, albeit missing many data types!
4. Made tests for konversation more robust, including test for
$ENV{'PYTHONPATH'} containing konversation in path, which I believe will work
for all new Konversations (KDE 5 and newer), and be much faster. The previous
tests are now more robust and less prone to failure, and only activate when
PYTHONPATH is not present with konversation string present as well.
5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs,
which can lead to wrong usable disk total size report, along with failure
to show components. Thanks delanym, issue #276 for reporting this problem, which
also exposed some harder to trigger bugs in ZFS (Bug 3).
6. Exposed by issue #276, case where line was wrapping value when value was too
short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words
trigger to enable wrapping of value, but noticed that if length of line was
exactly max-width, not > or <, it might vanish.
7. Case where no X or GPU drivers found, but dri driver detected, was not
showing, now does.
8. OpenRC is the init system in some cases, that is: readlink /sbin/init >
/sbin/openrc-init, where /proc/1/comm == init. Was showing only as OpenRC rc
type, which wasn't actually correct.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New nvidia gpu product ids for Turing, Ampere, Lovelace, Hopper. New Intel
GPU ids.
2. Added Zinc to systembase/distro, needs slightly special handling to get both
names right. Also added Tuxedo, which could use existing methods.
3. Added dpkg tool nala, which is sort of a CLI front end for apt, zinc uses it,
but it's also in Debian main package pool. Also deb-get, which is another zinc
thing for package management.
4. Full support for dinit: version, dinitctl w/status in ServiceData
4. Added initial support for init systems: 31init (31 line C program, no
--version), Hummingbird (unknown if -v/--version).
5. A few new CPU arch ids (new Intels).
--------------------------------------------------------------------------------
CHANGES:
1. Going somewhat along with the change in Audio to call ALSA a Sound API
instead of a sound server, changed key name OpenGL: to API: OpenGL in Graphics.
Also for EGL wayland, calling that the api too.
https://en.wikipedia.org/wiki/OpenGL
This conforms more closely to how these things are defined. Note that once
again, a value had been used as a key name, which almost always indicates a
failure to understand something about the core tech.
2. Changed wrapping of values from 3 words or more to 3 or more words AND length
> 24 characters. Saw example of:
.... used: 28.45 GiB
(4.5%)
which isn't desirable.
3. Changed minimum wrap to 60 columns, the new wrapper features are working so
well that if users want output that short, it will usually work fine, except of
course for very long word strings like a kernel name or parameter.
Note that this does not truncate long 'words' that might be wrapped, or going
along with Change 2, long 'sentences' of 2 words, those will always appear on
the same line regardless. For 'sentences' of 3 or more words, however, it goes
word by word, so it could well wrap after the first word, and so on. Obviously,
a 24 or fewer character value will never be wrapped, which was the intended
correction of change 2.
4. Going with Fix 8, OpenRc is an init system when it owns /proc/1/comm, had not
realized that /proc/1/comm == init can map to dinit, openrc as init. Now will
only show OpenRc as rc: type if not init as well.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updates in man for Change 1.
2. Added to docs/inxi-graphics.txt good quote re EGL/GBM, as well as VBE/GOP for
vesa. Trying to find docs where they actually say clearly it's an API is
remarkably difficult.
3. Man page, added note about Konversation requiring qdbus-qt5 (Debian+),
qt5-qttool (RHEL+/SUSE+), qt-tools (Arch+) for inxi to work inside it. Also
updated smxi.org/docs/inxi-usage.txt to note requirements for Konversation use
and setup.
4. Man, help, changed min width for -y/--width from 80 to 60.
5. docs/inxi-values.txt updated for --cygwin, --wsl fake OS type switches. Not
technically the OS, more the environment, but close enough.
6. docs/inxi-init.txt updated for new init types.
--------------------------------------------------------------------------------
CODE:
1. Refactored tools/gpu_ids.pl to correct and enhance some features.
2. Renamed functions and sections to better reflect that the display interface
is an API, this makes stuff less odd internally, and makes the function/variable
names correspond better to what the stuff really is.
3. Commented out kde konversation data source config collector, that logic looks
like it never worked, and couldn't work, since it never actually located
inxi.conf files, just paths to the data directories.
4. Expanded release.pl to handle acxi docs as well, makes it all consistent and
a lot easier to do long term.
5. Fake --wsl WSL switch, not really used, but in case.
6. Changed $b_cygwin to $windows{'cygwin'} and added $windows{'wsl'}.
7. Added -WSL to debugger string generator once WSL type is detected.
8. Refactored init, runlevel functions get_init_data() (now InitData::get()),
get_runlevel_data() (now InitData::get_runlevel()), get_runlevel_default() (now
InitData::get_runlevel_default()) into one package/class: InitData. This should
have been done a long time ago, to follow the general rule "if > 1 functions for
a tool refactor it into a class/package" for when to create a package/class
internally.
9. Completed gpu_ids.pl, now outputs the full hash set per item, so entire
blocks can be copied/pasted over. Something of a pain to get comments included,
which aren't strictly necessary in pinxi itself, but they do help read the
hashes for gpu data.
2022-10-31 22:47:31 +00:00
|
|
|
API: OpenGL renderer: AMD CEDAR (DRM 2.50.0 / 5.16.0-11.1\-liquorix-amd64 LLVM
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
12.0.1) v: 3.3 Mesa 21.2.6 compat\-v: 3.1 direct-render: Yes
|
2020-07-27 03:36:27 +00:00
|
|
|
....\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.fi
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Wayland sample, with Sway/swaymsg:
|
|
|
|
|
.nf
|
2022-07-27 21:10:52 +00:00
|
|
|
\fBinxi \-aGz
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Graphics:
|
Bug release, replace 3.3.17 asap, most users will not experience the bug, but if
they do, inxi stops right before the -D line. Failed to do an if defined test on
an array ref that could be undefined or an array ref. That makes Perl very
unhappy!
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. AMD family F, K8 series, will need more granular treatments to get the data
to be more accurate and less generic. We got 2 IDs nailed from raw visual data
confirmations and cpuid values, which leaves many, but good start. We will chip
away (pardon the pun) at these more ambiguous IDs over time, but don't need to
get them all done instantly, just eventually. Thanks slackware person linuxdaddy
for doing really good research and actually looking at the cpu to find dates
etc.
--------------------------------------------------------------------------------
BUGS:
1. Bug, fatal, caused by internal hash/array ref refactor of 3.3.17. Thanks
alaymari github issue #271 for reporting this one.
--------------------------------------------------------------------------------
FIXES:
1. None except for code fixes to try to avoid the cause of the bug in Bugs 1.
2. Fixed nvidia eol try --gpu, it was showing backwards, with --gpu, not
without, sigh.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added slimski dm data. That's a new fork of SLiM. Also guessing that brzdm
has same version -v output: brzdm version x.xx
--------------------------------------------------------------------------------
CHANGES:
1. None
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Refactors of core docs, ongoing, but will list those next release.
--------------------------------------------------------------------------------
CODE:
1. Cleaned up some array ref handling in subs, returned as: ($var1,$var2) =
@{block_data(...)}, skipped initializing and creating scalar to hold the ref,
just use it directly for DiskItem::block_data().
2. Also switched to local ref scalar array in DiskItem::scsi_data(),
DiskItem::block_data(). Not set local array, set local array ref, to keep it
clear. Also made DriveItem::drive_speed() return straight ref, not array then
ref. Same for many other subs, switched to ref assignment so it's the same ref
all through all the sub and return.
3. Fixed a redundant return \@$data to simply assinging to @$data ref, no return
needed, in DiskItem::smartctl_data().
4. Tightened some returns of ref so that tests if good test @$ref, not $ref.
Trying to avoid more cases like issue #271.
5. Going along with array ref local/return, switched all hash refs to local hash
ref returning ref, and working local with ref. More efficient, avoids creating
new refs over and over, dugh. This made a particularly large difference in CPU
because in certain parts, new references were being created over and over, and
subs were returning like \@arr or \%hash instead of declaring to start:
my $arr = []; my $hash = {};
Then working with the data from there on as an array or hash reference, to the
same original reference, rather than creating new ones over and over, which Perl
then has to track til they expire.
2022-06-13 23:32:32 +00:00
|
|
|
Device\-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
driver: radeon v: kernel alternate: amdgpu arch: TeraScale 2
|
|
|
|
|
process: TSMC 32\-40nm 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
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Display: wayland server: Xwayland v: 21.1.4 compositor: sway v: 1.6.1
|
|
|
|
|
driver: 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:
|
|
|
|
|
max: 1280x1024 min: 720x400
|
|
|
|
|
Monitor\-2: VGA-1 pos: primary,left model: DELL 1908FP serial: <filter>
|
|
|
|
|
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
|
This release fixes another very long standing bug, which I was not sure was an
inxi or a Konversation bug, which made tracking it down very difficult. Special
thanks to argonel of Konversation for helping solve this problem, or at least,
for directing my attention towards the likely cause area, and away from wrong
ideas. The bug was that inxi simply did not run in Konversation, it would exit
with error when run with /cmd or /inxi via symbolic links.
This may not seem like a huge deal to many of you, but the actual history of
inxi was directly linked to user support in mainly Konversation, so this feature
not working I have alwyas found extremely annoying, but I could never figure out
why it wasn't workiing, and didn't really know where to start until Argonel
helped narrow it down to a specific Konversation function in inxi. At which
point tracking down the real bug was fairly easy. Since testing in IRC is always
a key test point for inxi features and releases, not working in my main GUI IRC
client forced me to use CLI clients like irssi, via /exec -o inxi.
There was a secondary cause of failure, which was missing a key qdbus package,
which made figuring this one out a two step process.
So inxi is once again working in all areas, with no known significant failure
areas beyond known issues that have no current solution, or which I don't feel
like doing.
But possibly more important, a goal I have had for a while now of doing long
needed code refactors, bug fixes, without huge new code blocks or features
adding new future fixes and bugs, has been slowly happening.
This was quite important, because inxi's codebase and logic is so complex and
large now that at some point, it required rest and cleanup and corrections,
without continuously adding new code and logic, which would then trigger new
fixes and bugs. In other words, the code is taking a long needed, and well
deserved, breather, to recover after huge increases in the overall LOC and
feature sets.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. No known way to detect that the system might be Wayland for the Graphics:..
API: fixes, unless Xwayland is installed if the wayland protocol detections
failed, which they often do in console. Not practical to look for all compositor
variants on system to determine if it could be Wayland if not X or Xvesa, so
that one will just be what it is, which is fine, definitely better than it was
before. Note this is only an issue if in Console, no Display. Note that if inxi
is run as root, Wayland data also usually fails, even in Display.
--------------------------------------------------------------------------------
BUGS:
1. Another corner case monitor position issue, applied fallback primary monitor
rule when a primary monitor had already been located. This is corrected via a
graphics global $b_primary which once set will disable this fallback feature.
Objectively, the fallback feature should just be removed. The test is if that
monitor is not primary, and if position is 0x0, then assume primary, without
verifying no primary had been located yet.
2. A super old bug, in current konversation, was failing to trip the konvi
detections, which then resulted in not stripping off the first two args in
@ARGV, which then resulted in bad args being passed to inxi on konvi start,
which then resulted in silent failing. Many thanks to argonel of #konversation
for the patience to help me figure out what was going on with this bug. He's
been a Konversation developer probably longer than I've been doing inxi.
Cause was very tricky and subtle, the ps aux path for konvi had changed
slightly, not the path, but the pattern, it used to be:
konversation -session [sessin id]
but it's changed to:
konversation -qwindowtitle Konversation
or just plain:
konversation as line ending.
This led to failure to find konvi running, which then made the konvi ids fail.
Also, this would not work if the qdbus-qt5 package was not installed, or other
distros might have that packaged differently. Because of these dual causes, I
was simply unable to figure out what was going on for many years. I suspect this
stopped working with KDE 5/QT 5, but I'm not sure.
3. Used wrong key names for some ZFS tests and fallbacks, those could have led
to failures though very difficult to test and verify this. Also see fix 5, which
of course also looks like a bug, acts like one, but was actually due to a new
use of /dev/disk/by-partuuid for ZFS components in Ubuntu which inxi had not
seen before.
--------------------------------------------------------------------------------
FIXES:
1. Alternate ps IDs for appimage detection (try appimagelauncher), alternate
paths for possible appimage storage locations (also try ~/.appimage/*). File
names might be *.appimage or *.AppImage, probably other variants too.
2. Going along with Change 1, made tests more granular for missing graphics API
type data. Also updated messages to be more correct and clear, in and out of
display. This corrects an issue I'd seen but never resolved, which was on
headless systems showing this message:
Message: GL data unavailable in console. Try -G --display
Now the tests are far more granular, and only show that if glxinfo is installed,
and also shows specific messages if glxinfo not installed, but X/Xorg present,
or, for Wayland, if Xwayland present. These all get their own specific messages
now, and generally will also show which API is being used, or API: N/A if
nothing is detected, as in the case of a headless system with no X, Wayland,
etc.
3. Github issue #275 on of all things Microsoft WSL environment, has a small
glitch with undefined display hz, but otherwise inxi seems to work in that
environment, albeit missing many data types!
4. Made tests for konversation more robust, including test for
$ENV{'PYTHONPATH'} containing konversation in path, which I believe will work
for all new Konversations (KDE 5 and newer), and be much faster. The previous
tests are now more robust and less prone to failure, and only activate when
PYTHONPATH is not present with konversation string present as well.
5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs,
which can lead to wrong usable disk total size report, along with failure
to show components. Thanks delanym, issue #276 for reporting this problem, which
also exposed some harder to trigger bugs in ZFS (Bug 3).
6. Exposed by issue #276, case where line was wrapping value when value was too
short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words
trigger to enable wrapping of value, but noticed that if length of line was
exactly max-width, not > or <, it might vanish.
7. Case where no X or GPU drivers found, but dri driver detected, was not
showing, now does.
8. OpenRC is the init system in some cases, that is: readlink /sbin/init >
/sbin/openrc-init, where /proc/1/comm == init. Was showing only as OpenRC rc
type, which wasn't actually correct.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New nvidia gpu product ids for Turing, Ampere, Lovelace, Hopper. New Intel
GPU ids.
2. Added Zinc to systembase/distro, needs slightly special handling to get both
names right. Also added Tuxedo, which could use existing methods.
3. Added dpkg tool nala, which is sort of a CLI front end for apt, zinc uses it,
but it's also in Debian main package pool. Also deb-get, which is another zinc
thing for package management.
4. Full support for dinit: version, dinitctl w/status in ServiceData
4. Added initial support for init systems: 31init (31 line C program, no
--version), Hummingbird (unknown if -v/--version).
5. A few new CPU arch ids (new Intels).
--------------------------------------------------------------------------------
CHANGES:
1. Going somewhat along with the change in Audio to call ALSA a Sound API
instead of a sound server, changed key name OpenGL: to API: OpenGL in Graphics.
Also for EGL wayland, calling that the api too.
https://en.wikipedia.org/wiki/OpenGL
This conforms more closely to how these things are defined. Note that once
again, a value had been used as a key name, which almost always indicates a
failure to understand something about the core tech.
2. Changed wrapping of values from 3 words or more to 3 or more words AND length
> 24 characters. Saw example of:
.... used: 28.45 GiB
(4.5%)
which isn't desirable.
3. Changed minimum wrap to 60 columns, the new wrapper features are working so
well that if users want output that short, it will usually work fine, except of
course for very long word strings like a kernel name or parameter.
Note that this does not truncate long 'words' that might be wrapped, or going
along with Change 2, long 'sentences' of 2 words, those will always appear on
the same line regardless. For 'sentences' of 3 or more words, however, it goes
word by word, so it could well wrap after the first word, and so on. Obviously,
a 24 or fewer character value will never be wrapped, which was the intended
correction of change 2.
4. Going with Fix 8, OpenRc is an init system when it owns /proc/1/comm, had not
realized that /proc/1/comm == init can map to dinit, openrc as init. Now will
only show OpenRc as rc: type if not init as well.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updates in man for Change 1.
2. Added to docs/inxi-graphics.txt good quote re EGL/GBM, as well as VBE/GOP for
vesa. Trying to find docs where they actually say clearly it's an API is
remarkably difficult.
3. Man page, added note about Konversation requiring qdbus-qt5 (Debian+),
qt5-qttool (RHEL+/SUSE+), qt-tools (Arch+) for inxi to work inside it. Also
updated smxi.org/docs/inxi-usage.txt to note requirements for Konversation use
and setup.
4. Man, help, changed min width for -y/--width from 80 to 60.
5. docs/inxi-values.txt updated for --cygwin, --wsl fake OS type switches. Not
technically the OS, more the environment, but close enough.
6. docs/inxi-init.txt updated for new init types.
--------------------------------------------------------------------------------
CODE:
1. Refactored tools/gpu_ids.pl to correct and enhance some features.
2. Renamed functions and sections to better reflect that the display interface
is an API, this makes stuff less odd internally, and makes the function/variable
names correspond better to what the stuff really is.
3. Commented out kde konversation data source config collector, that logic looks
like it never worked, and couldn't work, since it never actually located
inxi.conf files, just paths to the data directories.
4. Expanded release.pl to handle acxi docs as well, makes it all consistent and
a lot easier to do long term.
5. Fake --wsl WSL switch, not really used, but in case.
6. Changed $b_cygwin to $windows{'cygwin'} and added $windows{'wsl'}.
7. Added -WSL to debugger string generator once WSL type is detected.
8. Refactored init, runlevel functions get_init_data() (now InitData::get()),
get_runlevel_data() (now InitData::get_runlevel()), get_runlevel_default() (now
InitData::get_runlevel_default()) into one package/class: InitData. This should
have been done a long time ago, to follow the general rule "if > 1 functions for
a tool refactor it into a class/package" for when to create a package/class
internally.
9. Completed gpu_ids.pl, now outputs the full hash set per item, so entire
blocks can be copied/pasted over. Something of a pain to get comments included,
which aren't strictly necessary in pinxi itself, but they do help read the
hashes for gpu data.
2022-10-31 22:47:31 +00:00
|
|
|
API: GBM/EGL
|
|
|
|
|
Message: Wayland GBM/EGL data currently not available.
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
.fi
|
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 18:59:56 +00:00
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-I\fR
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\- Adds to Packages number of lib packages detected per package manager. Also
|
|
|
|
|
adds detected package managers with 0 packages listed. Adds package manager
|
|
|
|
|
tools (supported: rpm, dpkg, pkgtool) Moves to \fBRepos\fR if \fB\-ra\fR.
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBinxi \-aI
|
|
|
|
|
Info:
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
....
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
Init: systemd v: 245 target: graphical.target (5) default: graphical.target
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
Compilers: gcc: 9.3.0 alt: 5/6/7/8/9 Packages: pm: apt pkgs: 3681 libs: 2096
|
|
|
|
|
tools: apt, apt\-get,aptitude pm: rpm pkgs: 0 Shell: ksh v: A_2020.0.0
|
|
|
|
|
default: Bash v: 5.0.16 running\-in: kate inxi: 3.1.04\fR
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.fi
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\- Adds service control tool, tested for in the following order: \fBsystemctl
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
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.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
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 18:59:56 +00:00
|
|
|
.B \-a \-j\fR (\fB\-\-swap\fR), \fB\-a \-P\fR [swap], \fB\-a \-P\fR [swap]
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- 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.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
For \fB\-P\fR per swap physical partition:
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBswappiness: 60 (default) cache\-pressure: 90 (default 100)\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
|
|
|
|
For \fB\-j\fR row 1 output:
|
|
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBKernel: swappiness: 60 (default) cache\-pressure: 90 (default 100)\fR
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- 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.
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
\- Adds device kernel major:minor number (Linux only).
|
|
|
|
|
|
|
|
|
|
.TP
|
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 18:59:56 +00:00
|
|
|
.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)
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- 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.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
|
|
|
|
\- Adds maj-min to LV and other devices.
|
|
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-m\fR
|
|
|
|
|
\- Expands volts to include curr/min/max values even if they are all identical.
|
|
|
|
|
|
Bug fixes!!! New Features!! Why wait!!!
Bugs:
1. Issue #220 on github: inxi misidentified XFCE as Gnome. This was a kind of core
issue, and pointed to some logic that needed updating, and some inadequate
assumptions made, and some too loose cascade of tests. Hopefully now xfce will
almost never get misidentified, and the other primary desktops ID'ed either from
$ENV or from xrop -root will be slightly more accurately identified as well.
Note that this fix creates a possibility for obscure misconfigured desktops to
be ID'ed wrong, but in this case, that will be technically a bug for them, but
with the new fixes, that situation will be cleaner to handle internally in the
desktop ID logic.
Also tightened the final Gnome fallback detection to not trigger a possible
false positive, it was testing for ^_GNOME but that is not adequate, because
some gnome programs will trigger these values in xprop -root even if GNOME
is not running. Should be safer now, hopefully no new bugs will be triggered
by these changes.
Fixes:
1. Missed an indentation level for -y1, gcc alt should have been indented in
one more level, now it is.
2. In disk vendors/family, didn't clean items starting with '/', this is
now corrected. Yes, some do, don't ask me why. Might be cases like:
Crucial/Micron maybe, where the first ID is grabbed, not sure.
Enhancements:
1. New Disk vendors, vendor IDs!!! The list never ends!!! We've finally found
infinity, and it is the unceasing wave of tiny and not so tiny disks and their
Ids.
2. New feature: for -Aa, -Na/-na/-ia, -Ga, now will add the modules the kernel
could support if they were available on the Device-x lines of those items.
This was made an -a option because it really makes no sense, if it's a regular
option, users might think that for example an nvidia card had a nouveua driver
when it didn't, when in fact, all the kernel is saying is that it knows those
listed modules 'couid' be used or present. This corresponds to the Display:
item in -Ga, that lists 'alternate:' drivers that Xorg knows about that could
likewise be used, if they were on the system.
In other words these are --admin options because otherwise users might get confused,
so this is one where you want to know the man explanation before you ask for it.
It is useful however if you're not sure what your choices are for kernel modules.
When the alternate driver is the same as the active driver, or if none is found,
it does not show the alternate: item to avoid spamming.
2020-07-27 02:22:59 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-n\fR, \fB\-a \-N\fR, \fB\-a \-i\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- Adds, if present, possible \fBalternate:\fR kernel modules capable of driving
|
|
|
|
|
each \fBDevice\-x\fR (not including the current \fBdriver:\fR). If no
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
non\-driver modules found, shows nothing. NOTE: just because it lists a module
|
|
|
|
|
does NOT mean it is available in the system, it's just something the kernel
|
|
|
|
|
knows could possibly be used instead.
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
|
|
|
|
|
\- Adds PCIe generation, and, if different than running PCIe generation, speed
|
|
|
|
|
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
|
|
|
|
|
shown).
|
|
|
|
|
|
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 18:59:56 +00:00
|
|
|
\- Adds for USB devices USB mode (Linux only).
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-o\fR
|
|
|
|
|
\- Adds device kernel major:minor number (Linux only).
|
|
|
|
|
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-p\fR,\fB\-a \-P\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds raw partition size, including file system overhead, partition table,
|
|
|
|
|
e.g.
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
\fBraw\-size: 60.00 GiB\fR.
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
|
|
|
|
|
\- Adds percent of raw size available to \fBsize:\fR item, e.g.
|
|
|
|
|
|
|
|
|
|
\fBsize: 58.81 GiB (98.01%)\fR.
|
|
|
|
|
|
|
|
|
|
Note that \fBused: 16.44 GiB (34.3%)\fR percent refers to the available size,
|
|
|
|
|
not the raw size.
|
|
|
|
|
|
|
|
|
|
\- Adds partition filesystem block size if found (requires root and blockdev).
|
|
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
\- Adds device kernel major:minor number (Linux only).
|
|
|
|
|
|
New version, new man, new feature!! Bug fixes!
Bugs:
1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it
was using unfiltered strings as regex pattern, and of course, a string flipped
an error. Fix was to add the regex cleaner to the string before it's used in test.
2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with
data or output so it couldn't be fixed. This was related to a syntax change in
usbdevs -v output in FreeBSD. Such changes are too common, but it might also
simply be a variant I have not seen or handled, but so far no data, so can't fix.
Don't blame me if you get this bug, but do post requested debugger data if you
want it fixed!
Fixes:
1. Updated man for weather, explained more clearly how to use country codes for
weather output. More clarifying in general about weather location, and weather
restrictions.
Enhancements:
1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from
liquorix for clarifying why that was a good idea. Note the initial issue came up
in a Debian issue report, not here. People!! please post issues here, and don't bug
maintainers with feature requests! Maintainers aren't in a position to add a feature,
so you should go straight to the source.
1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all
the flags, and also covers the short form flags and explains why they are used.
2. To resolve another issue, I made a new documentation file:
inxi-perl/docs/inxi-custom-recommends.txt
This is instructions for maintainers of distros who do not use rpm/apt/pacman but
still want the --recommends feature to output their package pool package names for
missing packages. I decided to not allow more than the default 3 package managers
because no matter what people say, if I allow in more, the maintainer will vanish
or lose interest, and I'll be stuck having to maintain their package lists forever.
Also, it's silly to even include that package list for any distro that does not
use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file
show what to change, and how, and has an example to make it clear. Odds of this
actually being used? Not high, lol, but that's fine, if people want it done, they
can do it, if not, nothing bad happens, it just won't show any suggested install
package, no big deal.
3. Using the new disk vendor method, added even more disk vendors. Thanks
linux litet hardware database!!
4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/
Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters,
from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me
where to look, I'll add it for those too, but wasn't anywhere I looked. Do the
BSDs even use that method? Don't know, but the logic is there, waiting to be used
if someone shows me how to get it cleanly. The 'parameters:' item shows in the main
'System:' -S output, and will just show the entire kernel parameters used to boot.
This could be very helpful to distros who often have to determine if for example
graphics blacklists are correctly applied for non free drivers, like nomodeset etc,
or if the opposite is present.
For forum/distro support, they just have to ask for: inxi -ba and they will see t
the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used
to trigger in this case the graphics and system lines.
5. Updated man/help for 4 as well, now explains what they will see with --admin/
-a options and -S. Good user suggestion, I wish all new features were this easy,
heh.
2019-05-01 00:56:10 +00:00
|
|
|
.TP
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.B \-a \-r\fR
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
\- Adds to \fBPackages:\fR report. See \fB\-Ia\fR
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-R\fR
|
|
|
|
|
\- Adds device kernel major:minor number (mdraid, Linux only).
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- Adds, if available, component size, major:minor number (Linux only). Turns
|
|
|
|
|
Component report to 1 component per line.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
New version, new man, huge update, bug fixes, cleanups, updates!!
What started as a relatively minor issue report ended up with a refactor of big
chunks of some of the oldest code and logic in inxi.
So many bugs and fixes, updates, and enhancements, that I will probably miss some
when I try to list them.
Bugs:
1. In the process of fixing an issue about sudo use triggering server admin
emails on failure, when --sudo/--no-sudo and their respective configuration
items were added, sudo was inadvertently disabled because the test ran before
the options were processed, which meant the condition to set sudo data was
always false, so sudo for internal use was never set. The solution was to
set a flag in the option handler and set sudo after options or configs run.
2. Issue #219 reported gentoo and one other repo type would fail to show
enabled repos, and would show an error as well, this was due to forgetting
to make the match test case insensitive. If only all bugs were this easy
to fix!!
3. I'd seen this bug before, and couldn't figure out why it existed.
It turned out that the partition blacklist filters were running fine
in the main partition data tool, but I had forgotten to add in corresponding
lsblk partition data filters, lol, so when the logic went back and double
checked for missing partitions [this feature had been if i remember right
to be able to show hidden partitions, which the standard method didn't see,
but lsblk did, anyway, when the double check and add missing partitions
logic ran, inxi was putting back in the blacklisted partitions every time,
despite the original blacklists working well and as intended.
This was fixed by adding in all the required fs type blacklists, then
adding in comments above each black list reminding coders that if they
add or remove from one blacklist, they have to do the same on the other.
4. Found while testing something unrelated on older vm, the fallback
case for cpu bugs, which was supposed to show the basic /proc/cpuinfo
cpu bugs, was failing inexplicably because the data was simply being
put into the wrong variable name, sigh.
Fixes:
1. While not technically an inxi bug, it would certainly appear that way to
anyone who triggered it. We'd gotten issue reports before on this, but they
were never complete, so couldn't figure it out. Basically, if someone puts
inxi into a simple script that is $PATH [this was the missing fact needed to
actually trigger this bug in order to fix it], the script [not inxi], will
then enter into an endless loop as inxi queries it for its version number using
<script name> --version. This issue didn't happen if the script calling inxi
was not in PATH, which is why I'd never been able to figure it out before.
Only simple scripts with no argument handlers could trigger this scenario,
and only if they were in PATH.
Fixing this required refactoring the entire start get_shell_data logic, which
ended up with a full refactor of the program_version logic as well. The fix
was to expand the list of shells known by inxi so it would be able to recognize
when it was in a shell running a script running inxi.
This resulted in several real improvements, for instance, inxi will now almost
always be able to determine the actual shell running inxi, even when started
by something else. It will also never use --version attempts on programs it does
not know about in a whitelist.
So we lose slightly the abilty to get version data on unknown shells, but we
gain inxi never being able to trigger such an infinite loop situation.
2. As part of the program_version refactor, a long standing failure to get ksh,
lksh, loksh, pdksh, and the related posh shells, all of which ID their version
numbers only if they are running the command in themselves. The mistake had
been having the default shell run that command. These all now correctly identify
themselves.
3. As part of the wm upgrades, many small failures to ID version numbers, or
even wm's, in some cases, were discovered when testing, and corrected. Some
I had not tested, like qtile, and the lisp variants, were not being detected
correctly by the tests due to the way python or lisp items are listed in ps aux.
4. As part of the wm update and program_version refactor, updated and simplified
many desktop and wm detections and logic blocks. Ideally this makes them more
preditable and easy to work on for the future.
5. As some last tunings for the new -y1 key: value pair per line output option,
fixed some small glitches in -b indentation. Also improved RAID indenting,
and Weather, and made it all very clean and predictable in terms of indentations.
6. Something I'd slightly noticed but never done anything about, while testing
desktop fixes, I realized that for Desktop: item, dm: is a secondary data type,
but if it's Console:, then DM: is a primary data type, not a secondary one. So
now if Console: it becomes DM: whic makes sense, previously it implied a dm:
was used to start the console, which was silly. Also, since often the reason
it's Console: with no dm in the first place is that it's a server with no dm.
So now if console, and no dm detected, rather than showing DM: N/A it just
doesn't show dm at all.
7. As part of the overall core refactor, the print_data logic was also refactored
and simplified, by making -y1 a first class citizen, it led to significantly
different way of being able to present inxi data on your screen, and now
print_data logic is cleaner and reflects these changes more natively, all the
initial hacks to get this working were removed, and the logic was made to be
core, not tacked on.
8. A small thing also revealed in issue #219, battery data was not being
trimmed, not sure how I missed that, but in some cases, space padding was in the
values and was not removed, which leads to silly looking inxi output.
9. Several massive internal optimizations, which were tested heavily, led to
in one case, 8-900x faster execution the second time a data structure is used,
previously in program_values the entire list was loaded each time program_values
was called, now it's loaded into a variable on first load and the variable is
used for the tests after that. This was also done for the vendor_version for
disk vendors, which also features a very long data structure which can be
loaded > 1 times for instances where a system has > 1 disk.
I also tested while I was at it, to see if loading these tyeps of data structures,
arrays of arrays, or hashes of arrays, by reference, or by dereferencing their
arrays, was faster, and it proved that it's about 20% faster to not
dereference them, but to use them directly. So I've switched a number of the
fixed data structures internally do use that method.
Another tiny optimization was hard resetting the print_data iterator hash,
while this would never matter in the real world, it showed that resetting
the iterator hash manually was slightly more efficient than resetting it
with a for loop.
10. While not seen inside inxi, I updated and improved a number of the vm's
used to test inxi and various software detections, so now I have a good selection,
going back to 2008 or so, up to current. This is helpful because things like
shells and window managers and desktops come and go, so it is hard to test
old detections on new stuff when you can't install those anymore. You'll see
these fixes in many of the less well known window managers, and in a few of
the better known ones, where in some cases the detections were damaged.
11. As part of the program_version refactor, updated and fixed file based
version detections, those, ideally, will almost never be used. Hopefully
programmers of things like window managers, shells, and desktops, can
learn how to handle --version requests, even though I realize that's a lot
harder than copying someone's code and then rebranding as your own project, or
whatever excuse people have for not including a --version item in their softaware.
Enhancements:
1. As a result of the shell, start shell, shell parent refactors, inxi was able
to correctly in most cases deetermine also the user default shell and its verison,
so that was added as an -Ixxx option:
Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16
2. As part of the program_version refactor, a more robust version number
cleaner was made, which now allows for much more manipulation of the version
number string, which sometimes contains, without spaces, non version number '
info right before the actual version.
3. Many more wm IDs were created and tested, and some old virtual machines
that were used years ago were used again to test old window managers and
their IDs, as well as new vms created to test newer ones. Many version
IDs and WM ids were fixed in this process as well. All kinds of new ones
added, though the list is basiclaly endless so ideally inxi would only use
its internal data tables for window managers that have actual users, or did.
4. First wayland datatype, now it may show Display ID: with -Ga, so far that's
the only wayland screen/display data I can get reliably.
5. As part of the shell parent/started in: updates and fixes, added every shell
I could find, and installed and tested as many of them as possible to verify
that either they have no version method, or that their version method works.
This shell logic also is used to determine start parent. Obviously using
whitelists of things that can change over time isn't ideal, but there was no
way to actually do it otherwise. The best part of the fixes is that it's now
remarkably difficult to trick inxi into reporting the wrong shell, and it
generally will also get the default shell right, though I found cases in
testing where a shell when started replaces the value in $SHELL with itself.
6. I found a much faster and reasonably reliable way to determine toolkits
used by gtk desktops, like cinnamon, gnome, and a few others. Test is to
get version from gtk-launcher, which is MUCH faster than doing a package
version query on the random libgtk toolkit that might be tested, and actually
was tested for pacman, apt, and rpm in the old days, but that was removed
because it was a silly hack. It's possible that now and then gtk desktops
will be 0.0.1 versions off, but in most cases, the version matched, so I decided
to restore the tk: item for a selection of gtk or gnome based desktops.
So now gtk desktops, except mate, which of course will be using gtk 2 for a
while longer, toolkit version should be working again, and the new method
works on everything, unlike the old nasty hack that was used, which required
package queries and guessing at which gtk lib was actually running the desktop,
it was such a slow nasty hack that it was dumped a while ago, but this new
method works reliably in most cases and solves most of the issues.
7. As part of the overall program_versions refactor, the package version
tester tool was extended to support pacman, dpkg, and rpm, which in practical
terms covers most gnu/linux users and systems. Since this feature is literally
only used for ASH and DASH shell version detections, it was really just added
as a proof of concept, and because it fit in well with the new Package counts
feature of -I/-r.
8. Updated for version info a few other programs, added compositors as well.
9. Last but not least!! More disk vendor IDs, more disk vendors!! And found
another source to double check vendor IDs, that's good.
New Features:
1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most
package managers plus snap, flatpak, and appimage. I didn't test appimage so
I'm not 100% sure that works, but the others are all tested and work.
If -r, Packages shows in the Repos item as first row, which makes sense, packages,
repos, fits. Note that in some systems getting full package counts takes some
time so it's an -x option not default.
If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia,
the following data shows:
* -Ix or -rx: show total package counts: Packages: 2429
* -Ixx or -rxx: shows Packages then counts by package manager located. If there
was only one package manager with packages, the total moves from right after
Packages: to the package manager, like: Packages: apt: 3241 but if there were
for example 2 or more found, it would show the total then:
Packages 3245 apt:3241 snap: 4
* -Ia or -ra: adds package managers with 0 packages managed, those are not
show with -xx, and also shows how many of those packages per package manager
is a library type lib file.
Sample:
inxi -Iay1
Info:
Processes: 470
Uptime: 8d 10h 42m
Memory: 31.38 GiB
used: 14.43 GiB (46.0%)
Init: systemd
v: 245
runlevel: 5
Compilers:
gcc: 9.3.0
alt: 5/6/7/8/9
Packages:
apt: 3685
lib: 2098
rpm: 0
Shell: Elvish
v: 0.13.1+ds1-1
default: Bash
v: 5.0.16
running in: kate
pinxi: 3.1.04-1
2020-06-29 05:22:12 +00:00
|
|
|
.TP
|
New version, new man, new feature!! Bug fixes!
Bugs:
1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it
was using unfiltered strings as regex pattern, and of course, a string flipped
an error. Fix was to add the regex cleaner to the string before it's used in test.
2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with
data or output so it couldn't be fixed. This was related to a syntax change in
usbdevs -v output in FreeBSD. Such changes are too common, but it might also
simply be a variant I have not seen or handled, but so far no data, so can't fix.
Don't blame me if you get this bug, but do post requested debugger data if you
want it fixed!
Fixes:
1. Updated man for weather, explained more clearly how to use country codes for
weather output. More clarifying in general about weather location, and weather
restrictions.
Enhancements:
1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from
liquorix for clarifying why that was a good idea. Note the initial issue came up
in a Debian issue report, not here. People!! please post issues here, and don't bug
maintainers with feature requests! Maintainers aren't in a position to add a feature,
so you should go straight to the source.
1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all
the flags, and also covers the short form flags and explains why they are used.
2. To resolve another issue, I made a new documentation file:
inxi-perl/docs/inxi-custom-recommends.txt
This is instructions for maintainers of distros who do not use rpm/apt/pacman but
still want the --recommends feature to output their package pool package names for
missing packages. I decided to not allow more than the default 3 package managers
because no matter what people say, if I allow in more, the maintainer will vanish
or lose interest, and I'll be stuck having to maintain their package lists forever.
Also, it's silly to even include that package list for any distro that does not
use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file
show what to change, and how, and has an example to make it clear. Odds of this
actually being used? Not high, lol, but that's fine, if people want it done, they
can do it, if not, nothing bad happens, it just won't show any suggested install
package, no big deal.
3. Using the new disk vendor method, added even more disk vendors. Thanks
linux litet hardware database!!
4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/
Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters,
from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me
where to look, I'll add it for those too, but wasn't anywhere I looked. Do the
BSDs even use that method? Don't know, but the logic is there, waiting to be used
if someone shows me how to get it cleanly. The 'parameters:' item shows in the main
'System:' -S output, and will just show the entire kernel parameters used to boot.
This could be very helpful to distros who often have to determine if for example
graphics blacklists are correctly applied for non free drivers, like nomodeset etc,
or if the opposite is present.
For forum/distro support, they just have to ask for: inxi -ba and they will see t
the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used
to trigger in this case the graphics and system lines.
5. Updated man/help for 4 as well, now explains what they will see with --admin/
-a options and -S. Good user suggestion, I wish all new features were this easy,
heh.
2019-05-01 00:56:10 +00:00
|
|
|
.B \-a \-S\fR
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- Adds alternate kernel clock sources, if available (Linux only).
|
|
|
|
|
|
New version, new man, new feature!! Bug fixes!
Bugs:
1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it
was using unfiltered strings as regex pattern, and of course, a string flipped
an error. Fix was to add the regex cleaner to the string before it's used in test.
2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with
data or output so it couldn't be fixed. This was related to a syntax change in
usbdevs -v output in FreeBSD. Such changes are too common, but it might also
simply be a variant I have not seen or handled, but so far no data, so can't fix.
Don't blame me if you get this bug, but do post requested debugger data if you
want it fixed!
Fixes:
1. Updated man for weather, explained more clearly how to use country codes for
weather output. More clarifying in general about weather location, and weather
restrictions.
Enhancements:
1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from
liquorix for clarifying why that was a good idea. Note the initial issue came up
in a Debian issue report, not here. People!! please post issues here, and don't bug
maintainers with feature requests! Maintainers aren't in a position to add a feature,
so you should go straight to the source.
1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all
the flags, and also covers the short form flags and explains why they are used.
2. To resolve another issue, I made a new documentation file:
inxi-perl/docs/inxi-custom-recommends.txt
This is instructions for maintainers of distros who do not use rpm/apt/pacman but
still want the --recommends feature to output their package pool package names for
missing packages. I decided to not allow more than the default 3 package managers
because no matter what people say, if I allow in more, the maintainer will vanish
or lose interest, and I'll be stuck having to maintain their package lists forever.
Also, it's silly to even include that package list for any distro that does not
use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file
show what to change, and how, and has an example to make it clear. Odds of this
actually being used? Not high, lol, but that's fine, if people want it done, they
can do it, if not, nothing bad happens, it just won't show any suggested install
package, no big deal.
3. Using the new disk vendor method, added even more disk vendors. Thanks
linux litet hardware database!!
4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/
Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters,
from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me
where to look, I'll add it for those too, but wasn't anywhere I looked. Do the
BSDs even use that method? Don't know, but the logic is there, waiting to be used
if someone shows me how to get it cleanly. The 'parameters:' item shows in the main
'System:' -S output, and will just show the entire kernel parameters used to boot.
This could be very helpful to distros who often have to determine if for example
graphics blacklists are correctly applied for non free drivers, like nomodeset etc,
or if the opposite is present.
For forum/distro support, they just have to ask for: inxi -ba and they will see t
the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used
to trigger in this case the graphics and system lines.
5. Updated man/help for 4 as well, now explains what they will see with --admin/
-a options and -S. Good user suggestion, I wish all new features were this easy,
heh.
2019-05-01 00:56:10 +00:00
|
|
|
\- Adds kernel boot parameters to \fBKernel\fR section (if detected). Support
|
|
|
|
|
varies by OS type.
|
|
|
|
|
|
Bug fix, it's a bad edid data bug, rare, but when it trips, kills inxi execution
dead right before -G/Graphics shows. Also some nice fixes and enhancements.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Possible case of Gnome Wayland failing to set any gnome environmental
variables, making wayland detection not possible. This was in anonymous dataset
inxi-proBook4540s dataset. Person never appeared in real life so can't follow up
on it. This cascaded down to other failures in display detection, and desktop
detection, though in theory much of the data needed was present. I expect
similar issues may appear with kde wayland. This is/was probably a configuration
or build error I believe, though not enough data yet.
It appears that sudo start disabled the display environmental variable
detections, which is unfortunate, and the fallback loginctl tests do not appear
to work for unknown reasons. I've confirmed this on Fedora stock Gnome as well.
--------------------------------------------------------------------------------
BUGS:
1. Forgot to test that return from get_display_manager is array ref, this
impacts only a tiny handful of distros probably, TinyCore was one, but it is
a fatal failure, so fixed it. Also fixed in 3.3.14 inxi branch. Never trips in
console, only on tiny linux where no dm is used at all, I think Xvesa might be
the only case this would have tripped.
2. EDID errors and warnings had several bugs, errors a fatal critical bug which
made execution stop. Had forgotten to pass the $edid hash reference to the error
constructor. Also had used wrong hash key in output so would never have shown.
--------------------------------------------------------------------------------
FIXES:
1. Corrected ram device indentation levels.
2. Made memory width more clear with: width: data: total: which more
accurately reflects the source data. Also in cases where no data or total
values, only show width: N/A, not the data: total: sub items.
3. Made edid errors/warnings output to numbered list of warnings/errors instead
of using join() to made one long list. Much more consistent that way. This fixes
issue #266 - thanks SheridanOAI for finding this bug.
4. In --slots, -x wasn't loading the bus ID so it showed N/A, unnecessary data
collection granularity, removed.
5. For Display, if no X or gpu driver, show: driver: N/A. Showed driver: gpu:
N/A before.
6. For Display, remove filters for Xwayland tests, we always want to see
xwayland data if it's installed. This was actually an error to not show it since
display_server_data already had the correct tests to not redo Xorg data if found
previously, which would be glxinfo based data. This is a partial fix also for
Known Issue 1, at least we'll see Xwayland is present even if Wayland detections
failed for unkonwn reasons.
7. Added some ram value dmi filters, found some that had 'none' or 'unknown'.
8. Show display protocol out of display!! Also handles most common root use
cases as well, so in most cases, if the initial protocol detections failed, this
will result in a decent attempt, though if root it is less reliable. sudo or
regular user will be fine since looks for not tty/pts TTY type and username.
This should also help narrow down Known Issue 1 failures, though there are more
cases to be dealt with, but can only chip away since not enough data.
9. Made info: item in slots more robust, and able to handle more diverse
scenarios.
10. Added alternate syntaxes for dmidecode permissions errors.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added brzdm clogin mlogind xlogin display managers. Not verified. Version for
brzdm is probably like slim since brzdm is a fork of slim.
2. Added voltages to ram module report, that had been left out. Note that it's
common for voltages to be either 'unknown' or not present at all. This is as
close as inxi can get to handling issue #265 since there is no other source for
the requested data type (show DDR3L, low voltage DDR3, which doesn't exist as a
type in dmidecode).
3. Added voltages to --slots report, --slots -xx. Only shows if present.
4. Added for --slots -a for Linux, if detected, the PCI children of the bus ID
of the slot. This is recursive, so supports as many levels as are present,
though it would be rare for there to be more than one level of children.
--------------------------------------------------------------------------------
CHANGES:
1. In -m ram report, moved ram type before size/speed/voltage, that makes more
sense.
2. Also in -m ram report, make type: the default value (was an -x options
before), which contains the no module found messages etc, making the order:
Device-1: DIMM 0 type: no module installed
Device-2: DIMM 1 type: DDR4 size: 16 GiB speed: 2400 MT/s
This puts all the speed/size/voltage data together, and stops putting the no
module found message in speed, which never made any sense.
2. In -m, changed width data to more clearly reflect the data source:
width (bits):
data: 64
total: 72
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, added a TABLE OF CONTENTS section which lists all the primary
sections. Can help since the man page has gotten so darned long and man doesn't
as far as I know support clickable internal links, sadly.
2. For -m, updated for revised output syntax and -x levels. Note that the help
and man actually had the type: as default for -m, not -mx, but for some reason,
the code had it wrong. Oops.
3. For -m, fixed some legacy output syntax in the examples.
--------------------------------------------------------------------------------
CODE:
1. Some refactors of slots, ram, as well as a bit more refactoring of edid stuff
for graphics.
2. Added $ENV{'DISPLAY'} to debugger data collector, no idea why that was left
out.
2022-04-08 05:49:36 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-a \-\-slots\fR
|
|
|
|
|
\- Adds PCI children of the main slot bus ID, and their types and class IDs,
|
|
|
|
|
recursively. Linux only, and only if detected. Sample:
|
|
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBSlot: 0
|
|
|
|
|
type: PCIe
|
|
|
|
|
lanes: 16
|
|
|
|
|
status: in use
|
|
|
|
|
length: long
|
|
|
|
|
volts: 3.3
|
|
|
|
|
bus\-ID: 00:03.1
|
|
|
|
|
children:
|
|
|
|
|
1: 07:00.0
|
|
|
|
|
class\-ID: 0300
|
|
|
|
|
type: display
|
|
|
|
|
2: 07:00.1
|
|
|
|
|
class\-ID: 0403
|
|
|
|
|
type: audio\fR
|
|
|
|
|
.fi
|
|
|
|
|
|
New version, updated man page, new tarball.
Fixed partition bug that could falsely identify a remote filesystem like nfs as /dev fs
Added two options:
-! 31 - Turns off Host section of System line. This is useful if you want to post output
from server without posting its name.
-! 32 - Turns on Host section if it has been disabled by user configuration file
B_SHOW_HOST='false'
Added missing CPU data message, fixed missing cpu cache/bogomips output, turned off
bogomips if null for bsd systems because bogomips is a linux kernel feature.
Added N/A for no memory report, this would mainly hit bsd systems where user has no
permissions to use sysctl or has no read rights for /var/run/dmesg.boot.
Many fixes for partitions, now for bsd, if available, uses gpart list to get uuid/label
Added support for raid file system syntax in bsd, now excludes main raid device name,
and adds a flag to raiddevice/partitionname type so output can identify it as a raid
slice/partition.
In man page, added -! 31 / -! 32 sections, and some other small edits.
Added bsd raid line error message, added bsd sensors line error message.
Many other small bug fixes that should make linux more robust in terms of missing
data, and better/cleaner output for bsd.
2013-02-18 20:33:05 +00:00
|
|
|
.SH ADVANCED OPTIONS
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-alt 40\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Bypass \fBPerl\fR as a downloader option. Priority is: Perl (HTTP::Tiny), Curl,
|
|
|
|
|
Wget, Fetch, (OpenBSD only) ftp.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-alt 41\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Bypass \fBCurl\fR as a downloader option. Priority is: Perl (HTTP::Tiny), Curl,
|
|
|
|
|
Wget, Fetch, (OpenBSD only) ftp.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-alt 42\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Bypass \fBFetch\fR as a downloader option. Priority is: Perl (HTTP::Tiny), Curl,
|
|
|
|
|
Wget, Fetch, (OpenBSD only) ftp.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-alt 43\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Bypass \fBWget\fR as a downloader option. Priority is: Perl (HTTP::Tiny), Curl,
|
|
|
|
|
Wget, Fetch, OpenBSD only: ftp
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-alt 44\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Bypass \fBCurl\fR, \fBFetch\fR, and \fBWget\fR as downloader options. This
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
basically forces the downloader selection to use \fBPerl 5.x\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\fBHTTP::Tiny\fR, which is generally slower than \fBCurl\fR or \fBWget\fR but it
|
|
|
|
|
may help bypass issues with downloading.
|
2017-06-09 02:29:55 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
.TP
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
.B \-\-bt\-tool [bt\-adapter|btmgmt|hciconfig|rfkill]\fR
|
|
|
|
|
See \fB\-\-force [tool name]\fR. Used to set \fB\-E\fR report tool.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-dig\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Temporary override of \fBNO_DIG\fR configuration item. Only use to test w/wo
|
|
|
|
|
dig. Restores default behavior for WAN IP, which is use dig if present.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2017-06-09 02:29:55 +00:00
|
|
|
.TP
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
.B \-\-display [:<integer>]\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Will try to get display data out of X (does not usually work as root user).
|
|
|
|
|
Default gets display info from display \fB:0\fR. If you use the format
|
|
|
|
|
\fB\-\-display :1\fR then it would get it from display \fB1\fR instead, or any
|
|
|
|
|
display you specify.
|
2017-06-10 21:42:49 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Note that in some cases, \fB\-\-display\fR will cause inxi to hang endlessly
|
|
|
|
|
when running the option in console with Intel graphics. The situation regarding
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
other free drivers such as nouveau/ATI is currently unknown. It may be that this
|
|
|
|
|
is a bug with the Intel graphics driver \- more information is required.
|
2017-06-10 21:42:49 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
You can test this easily by running the following command out of X/display
|
|
|
|
|
server: \fBglxinfo \-display :0\fR
|
2017-06-10 21:42:49 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
If it hangs, \fB\-\-display\fR will not work.
|
2017-06-09 02:29:55 +00:00
|
|
|
|
2018-03-24 09:18:41 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-dmidecode\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Shortcut. See \fB\-\-force dmidecode\fR.
|
2018-03-24 09:18:41 +00:00
|
|
|
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-downloader [curl|fetch|perl|wget]\fR
|
2018-04-04 06:41:06 +00:00
|
|
|
Force inxi to use Curl, Fetch, Perl, or Wget for downloads.
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
.TP
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
.B \-\-force [option(s)]\fR
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
Various force options to allow users to override defaults. Values can be given
|
|
|
|
|
as a comma separated list:
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
|
|
|
|
\fBinxi \-MJ --force dmidecode,lsusb\fR
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- \fBbt\-adapter\fR \- Force use of bt\-adapter tool in \fB\-E\fR.
|
|
|
|
|
|
|
|
|
|
\- \fBbtmgmt\fR \- Force use of btmgmt tool in \fB\-E\fR.
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\- \fBcolors\fR \- Same as \fB\-Y \-2\fR . Do not remove colors from piped or
|
|
|
|
|
redirected output.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- \fBdmidecode\fR \- Force use of \fBdmidecode\fR. This will override
|
|
|
|
|
\fB/sys\fR data in some lines, e.g. \fB\-M\fR or \fB\-B\fR.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
|
|
|
|
\- \fBhddtemp\fR \- Force use of hddtemp instead of /sys temp data for disks.
|
|
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- \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).
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- \fBlsusb\fR \- Forces the USB data generator to use \fBlsusb\fR as data
|
|
|
|
|
source (default). Overrides \fBUSB_SYS\fR in user configuration file(s).
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
\- \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
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
command:
|
Many small updates, enhancements, bug fixes!!! We've been saving them up!! Here
they are!! Don't wait!!
Thanks mr. mazda for many issue finds, and suggestions.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. Due to unfixable rpm slowdowns, removed package counts for default output for
rpm based systems. We were seeing delays of up to 30+ seconds just to list the
rpm package count, which is absurd, even after the rpm optimizations inxi
already runs. To allow rpm users to get excluded by default for rpm package list
counts, added --pkg flag plus a short message telling them to use that flag to
get the installed package count if they want it.
Changes like this are very unfortunate, but in 2021 for a package manager at
times to require over 30 seconds to generate a trivial installed package list is
just not acceptable. One of the reasons this release was delayed was this was
not an easy decision to make, it's very rare support for a feature is removed
for specific tools due to how badly the tools may perform. Note that whatever
higher level tool is used, like dnf, zypp, it's still the same speed, they all
appear to use the same core engine.
Basically this decision was forced since either inxi looks really bad and slow,
when it's not, or the actual cause was removed from default outputs.
--------------------------------------------------------------------------------
BUGS:
1. Small bug in nfs blacklist for disk used led to nfs used being added, which
leads to silly used percents. This is corrected.
2. If ram vendor ID failed, inxi would delete the part number. Oops. This was
related to the Mushkin failures.
3. Close to a bug, though not one internally, but to users would appear as one:
ZFS does not act as expected, zpool list did not in fact return the pool size,
which I had always assumed to be the case, but in a very strange decision, does
return something very close to the pool size for mirrors, but NOT for z1 or z2
pools, then it returns the total size of the drives that make up the pool. To
call this strange behavior would be an understatement. The fix was to modify the
logic to use zfs list instead to get the size data. This also makes the drive
total report far more accurate, since it lists usable space now for ZFS as was
always intended. The cause of this was simply that I'd always had access to zfs
mirrors, not z1 or z2 arrays.
--------------------------------------------------------------------------------
FIXES:
1. OpenSuse and maybe others use kdm3 for Trinity, not kdm, so dm was failing.
2. Going along with fix 1, made kde version detection more robust so may catch
more fringe / corner cases for kde desktops. These were mainly added to correct
Trinity desktop version detections.
3. Mushkin ram vendor ID was failing, that is or should be corrected.
4. Added in /dev/disk/by-id handlers for zpool components, there are several
variants, wwn-, pci-, scsi-, ata-, but they all map to the real /dev drive IDs.
Failure to unmap these led to failing to match components and get size info
etc for zfs.
5. See DOCUMENTATION: 2, language changes for weather feature abuse.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo
types. Not sure how that one was missed, but there it is. This should tighten
repo reports for dnf/yum/zypp types.
2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for:
penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2.
3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
since xfwm can run in compositing or non compositing mode. But should show
since many users use compositing mode now.
4. Added OpenMediaVault distro ID and systembase handlers.
5. Going along with zfs bug fix 3, using zfs list data for free, size,
allocated. Trying to understand how zfs developers actually thought about this
is nearly impossible so just used what seems to correspond to reality most.
Also shows raw values for zfs data in RAID along with regular ones to make
clear which is which value.
6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
Both vendors finally released some new CPUs and the data became available,
which doesn't always happen quickly.
7. A bunch of new disk vendors and vendor IDs added. Never stops, like the
sands of time, like the ocean waves, like the scuttling crabs scrounding around
in the seaweed in the foam where the outgoing wave left its mark...
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added leftwm keybindinigs to inxi-data.txt desktop/wm section. Updated more
wm in that section as well, and list more info on wms for future reference etc.
Also reorganized and more more readable wm section.
2. Help/Man now make more clear that automated requests or excessive use of the
inxi weather feature are not under any circumstance permitted. There had been
some ambiguity and lack of clarity about what abuse is, now it should be more
clear.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Refactored uptime parser logic, the code and regex was just getting too
messy and difficult to work with and debug, now it works similar to how the
revised BSD parsers run, the regex are pulled apart and made more granular so
a small syntax change ideally won't break the detections as easily.
2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
time I notice that almost invariably stuff done to save lines of code makes
code harder to read as the feature expands, so it's generally worth just
unravelling it so it all stacks and is easy to scan/read. Also removed extra
white space in parens, which is something I'm leaning more towards but it's
not worth fixing all at once so it's just done where it's noticed.
That's using:
if ( /test/ ){
rather than:
if (/test){
I believe using more white space helped with Perl comprehension in the
intermediate stages, but is not required anymore and just looks like extra
whitespace now.
2021-07-12 02:32:13 +00:00
|
|
|
|
|
|
|
|
.nf
|
|
|
|
|
\fBrpm \-qa \-\-nodigest \-\-nosignature\fR
|
|
|
|
|
.fi
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
Even on newer rpm systems, in virtual machines, running rpm package list query
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
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.
|
|
|
|
|
Older systems have taken up to 30 seconds to run this command!
|
|
|
|
|
|
|
|
|
|
For systems that support running rpm along with the primary package installer
|
|
|
|
|
(dpkg/apt, pacman, and pkgtool/slackpkg), there are not going to be many rpms,
|
|
|
|
|
if any, installed, so the command runs in those cases (if inxi can determine it
|
|
|
|
|
is running in that type of system).
|
Many small updates, enhancements, bug fixes!!! We've been saving them up!! Here
they are!! Don't wait!!
Thanks mr. mazda for many issue finds, and suggestions.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. Due to unfixable rpm slowdowns, removed package counts for default output for
rpm based systems. We were seeing delays of up to 30+ seconds just to list the
rpm package count, which is absurd, even after the rpm optimizations inxi
already runs. To allow rpm users to get excluded by default for rpm package list
counts, added --pkg flag plus a short message telling them to use that flag to
get the installed package count if they want it.
Changes like this are very unfortunate, but in 2021 for a package manager at
times to require over 30 seconds to generate a trivial installed package list is
just not acceptable. One of the reasons this release was delayed was this was
not an easy decision to make, it's very rare support for a feature is removed
for specific tools due to how badly the tools may perform. Note that whatever
higher level tool is used, like dnf, zypp, it's still the same speed, they all
appear to use the same core engine.
Basically this decision was forced since either inxi looks really bad and slow,
when it's not, or the actual cause was removed from default outputs.
--------------------------------------------------------------------------------
BUGS:
1. Small bug in nfs blacklist for disk used led to nfs used being added, which
leads to silly used percents. This is corrected.
2. If ram vendor ID failed, inxi would delete the part number. Oops. This was
related to the Mushkin failures.
3. Close to a bug, though not one internally, but to users would appear as one:
ZFS does not act as expected, zpool list did not in fact return the pool size,
which I had always assumed to be the case, but in a very strange decision, does
return something very close to the pool size for mirrors, but NOT for z1 or z2
pools, then it returns the total size of the drives that make up the pool. To
call this strange behavior would be an understatement. The fix was to modify the
logic to use zfs list instead to get the size data. This also makes the drive
total report far more accurate, since it lists usable space now for ZFS as was
always intended. The cause of this was simply that I'd always had access to zfs
mirrors, not z1 or z2 arrays.
--------------------------------------------------------------------------------
FIXES:
1. OpenSuse and maybe others use kdm3 for Trinity, not kdm, so dm was failing.
2. Going along with fix 1, made kde version detection more robust so may catch
more fringe / corner cases for kde desktops. These were mainly added to correct
Trinity desktop version detections.
3. Mushkin ram vendor ID was failing, that is or should be corrected.
4. Added in /dev/disk/by-id handlers for zpool components, there are several
variants, wwn-, pci-, scsi-, ata-, but they all map to the real /dev drive IDs.
Failure to unmap these led to failing to match components and get size info
etc for zfs.
5. See DOCUMENTATION: 2, language changes for weather feature abuse.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going along with the rpm issues, added dnf.conf support to yum/dnf repo
types. Not sure how that one was missed, but there it is. This should tighten
repo reports for dnf/yum/zypp types.
2. Added LeftWM. LeftWM confirmed working. Added unverifed detections for:
penrose, 2bwm, 5dwm, catwm, mcwm, monsterwm, snapwm, uwm, wingo, wmfs, wmfs2.
3. Added xfwm as a compositor type, that had bee left out, somewhat on purpose,
since xfwm can run in compositing or non compositing mode. But should show
since many users use compositing mode now.
4. Added OpenMediaVault distro ID and systembase handlers.
5. Going along with zfs bug fix 3, using zfs list data for free, size,
allocated. Trying to understand how zfs developers actually thought about this
is nearly impossible so just used what seems to correspond to reality most.
Also shows raw values for zfs data in RAID along with regular ones to make
clear which is which value.
6. Added more CPU architecture ID matches for AMD Zen and a variety of Intel.
Both vendors finally released some new CPUs and the data became available,
which doesn't always happen quickly.
7. A bunch of new disk vendors and vendor IDs added. Never stops, like the
sands of time, like the ocean waves, like the scuttling crabs scrounding around
in the seaweed in the foam where the outgoing wave left its mark...
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Added leftwm keybindinigs to inxi-data.txt desktop/wm section. Updated more
wm in that section as well, and list more info on wms for future reference etc.
Also reorganized and more more readable wm section.
2. Help/Man now make more clear that automated requests or excessive use of the
inxi weather feature are not under any circumstance permitted. There had been
some ambiguity and lack of clarity about what abuse is, now it should be more
clear.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Refactored uptime parser logic, the code and regex was just getting too
messy and difficult to work with and debug, now it works similar to how the
revised BSD parsers run, the regex are pulled apart and made more granular so
a small syntax change ideally won't break the detections as easily.
2. Cleaned up sub cpu_arch() and made all the arch values line up nicely, over
time I notice that almost invariably stuff done to save lines of code makes
code harder to read as the feature expands, so it's generally worth just
unravelling it so it all stacks and is easy to scan/read. Also removed extra
white space in parens, which is something I'm leaning more towards but it's
not worth fixing all at once so it's just done where it's noticed.
That's using:
if ( /test/ ){
rather than:
if (/test){
I believe using more white space helped with Perl comprehension in the
intermediate stages, but is not required anymore and just looks like extra
whitespace now.
2021-07-12 02:32:13 +00:00
|
|
|
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
\- \fBsensors\-sys\fR \- Force use of \fB/sys/class/hwmon\fR data for sensors
|
|
|
|
|
(excluding ipmi sensors, which are their own line if present), skip
|
|
|
|
|
\fBlm\-sensors\fR. Generally useful for testing since sys data is used if no
|
|
|
|
|
lm\-sensors data was found anyway, but if \fBlm\-sensors\fR was installed, and
|
|
|
|
|
returned no data, it's most likely if not nearly certain that \fB/sys\fR will
|
|
|
|
|
also not return data.
|
|
|
|
|
|
|
|
|
|
\- \fBusb\-sys\fR \- Forces the USB data generator to use \fB/sys\fR as data
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
source instead of \fBlsusb\fR (Linux only).
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
|
|
|
|
\- \fBvmstat\fR \- Forces use of vmstat for memory data.
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
\- \fBwayland\fR \- Forces use of Wayland, disables x tools glxinfo, xrandr,
|
|
|
|
|
xdpyinfo.
|
|
|
|
|
|
|
|
|
|
\- \fBwmctrl\fR \- Force \fBSystem\fR item \fBwm\fR to use \fBwmctrl\fR as data
|
|
|
|
|
source, override default \fBps\fR source.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-hddtemp\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Shortcut. See \fB\-\-force hddtemp\fR.
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-html\-wan\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Temporary override of \fBNO_HTML_WAN\fR configuration item. Only use to test
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
w/wo HTML downloaders for WAN IP. Restores default behavior for WAN IP, which is
|
|
|
|
|
use HTML downloader if present and if dig failed.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
2023-08-16 03:07:26 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-ifconfig\fR
|
|
|
|
|
Shortcut. See \fB\-\-force ifconfig\fR.
|
|
|
|
|
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-man\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Updates / installs man page with \fB\-U\fR if \fBpinxi\fR or using \fB\-U 3\fR
|
|
|
|
|
dev branch. (Only active if \fB\-U\fR is is not disabled by maintainers).
|
New version, new man. Big update, corrects many small typos, adds some good new
features.
So now inxi and pinxi will grab the inxi.1 or pinxi.1 man file and install it on
systems that do not have -U blocked. The -U block of course remains the same.
New features:
1. now does not require root or 'file' to get unmounted fs type. Also, for many
mounted partitions, rather than showing the meaningless fuseblock it will usually
get the filesystem right.
2. -U now works with optional --man option to download man page for pinxi
and -U 3 dev server updates. This gets around the fact I had to remove the gz files
from master to get the size small enough to make maintainers happy. Non branch
inxi master works as before, updates both from github or from dev server, depending
on your selection.
3. Thanks very much to the people who have been contributing in a positve way,
helping to make inxi better. The untold number of small and large new features,
small glitches, etc, that have been fixed this week are simply too many too list.
Many to most were inxi bugs or weaknesses, now corrected.
4. binxi branch has now been made fully operational, though I do not plan on doing
any work beyond the mothballing of that venerable program (gawk->bash inxi), it's
fully operational, it updates, it gets its man page, but all as binxi, so you can,
as with pinxi, run all of them separately. This officially terminates my support
for Gawk/Bash inxi, which can be found as binxi in the inxi-legacy branch.
5. pinxi has been promoted to permanent development branch, where bug fixes, new
features, etc, will be tested, along with man page updates etc. This will help
reduce the number of commits to master branch.
6. Audio / Network usb cards now show the true driver(s). There are often more
than one for audio, that's a nice enancement.
7. inxi outputs to json / xml, which will probably interest some developers
eventually, well it already did, that was going to wait, but someone wanted it.
8. Apt repo handler now supports DEB822 format, which is not an easy format to
parse.
==========================================================
MAINTAINERS:
Note the following: despite my strong dislike for tags, every commit that touches
either inxi or inxi.1 man page will be tagged if I think they would be something
relevant to distro packagers. While github insists on calling my tags releases,
I want to be crystal clear: inxi has one and only one 'release', the current master
branch version. The tagged commits that github calls releases are NOT releases,
they are just tagged commits. The version I release tomorrow will be the current
master, and all previous versions will be obsolete and will not be supported.
The .gz files have been removed from the master branch history, thus shrinking it
a lot. I have removed for this reason the master-plain branch, which mirrored
master and provided a gz free branch, but apparently this was simply ignored so
there's no reason to keep it going. If you insist on grabbing all the branches and
find more data in there, then please correct your practices, you are only getting
the data from the master branch.
inxi is rolling release software and has no releases, so the tags are supposed
to create some illusion that a tag actually means something. Since it doesn't,
I decided to take the path of least resistance and just add an auto tagging tool
to my commit scripts and use it when it seems appropriate, like on this commit.
All development work now will happen via the pinxi branch, so that makes the process
a lot cleaner, since I can now basically beta test all new commmits to master.
pinxi and binxi are both standalone versions of inxi, they have their own config
and data directories, config files, man pages, etc.
-----------------------------------------------------
New Perl inxi is already way ahead of Gawk/Bash inxi, more features, more accurate,
and most bugs being fixed now are because a lot of people are contributing eyes and
testing, and are finding stuff that was wrong, or simply missing, on old inxi as
well as on Perl inxi. Fixes to Perl inxi (>2.9) will not be rolled into to binxi
since the entire reason I spent over 4 months on this project was to never have to
touch Gawk/Bash inxi again.
Most imporant, however, is that the simple fact was, Gawk/Bash inxi has been
nearly impossible to work on despite my following rigorous practices in coding,
and I simply won't work with that type of stuff anymore. Perl 5.x is a true delight
in comparison, and makes adding new features, enhancing others, far easier, or
even possible, where it wasn't before.
On a technical level, I have tested Perl inxi heavily, and it will run on all
Perl 5.x versions back to 5.008, which is the cutoff point. This was not that
hard to do, which is why I picked Perl 5.x as the language. This means that
you can drop, just as with binxi, Perl inxi onto a 10 year old system, or
older, and it will run fine, albeit a touch slowly, but must faster than binxi.
-----------------------------------------------------
So far users are really liking the new one, it's usually faster in most cases,
the output is cleaner, there's more data, more options, and basically it's
gotten the thumbs up from all the testers, and there have been a LOT, who have
helped. I want to give a special thanks to the following distros for their
exceptional support and testing:
0. the people who hang out on irc.oftc.net #smxi. Very patient, will test things
with astounding patience, so thanks to them. Archerseven, iotaka and KittyKatt
have been been incredibly helpful when it comes to testing and debugging, and
finding corner cases that I would never have found.
1. AntiX: they were the first to beta test pinxi, and found massive numbers of
bugs, and stuck with the testing for a long time. They made testing possible for
the next wave of testers, my hats off to them, I've always liked them.
2. Manjaro also was very helpful, and found more issues and enhancements.
3. Ubuntu forums users found more, and helped enhance many faetures
4. Mint users have been very helpful, and were the impetus for some nifty
new features, ilke switching all color codes off when output is piped or sent
to file. They have reminded me of how valuable people's views can be who may not
share the same tech world view as you, but are still very talented and observant
individuals.
5. Slackware users provided some very thoughtful feedback, which was no surprise
but welcome nonetheless, thanks.
6. Same with Debian forums, again, some very useful and constructive ideas and
observations, and some very arcane and odd hardware that exposed even more corner
case bugs.
And several other distros were also helpful, each in their own way. Solus for
example now has their package manager added in repos.
2018-03-23 05:59:34 +00:00
|
|
|
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-dig\fR
|
|
|
|
|
Overrides default use of \fBdig\fR to get WAN IP address. Allows use of normal
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
downloader tool to get IP addresses. Only use if dig is failing, since dig is
|
|
|
|
|
much faster and more reliable in general than other methods.
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-doas\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Skips the use of doas to run certain internal features (like \fBhddtemp\fR,
|
|
|
|
|
\fBfile\fR) with doas. Not related to running inxi itself with doas/sudo or
|
|
|
|
|
super user. Some systems will register errors which will then trigger admin
|
|
|
|
|
emails in such cases, so if you want to disable regular user use of doas
|
|
|
|
|
(which requires configuration to setup anyway for these options) just use
|
|
|
|
|
this option, or \fBNO_DOAS\fR configuration item. See \fB\-\-no\-sudo\fR if
|
|
|
|
|
you need to disable both types.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-html-wan\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Overrides use of HTML downloaders to get WAN IP address. Use either only dig,
|
|
|
|
|
or do not get wan IP. Only use if dig is failing, and the HTML downloaders are
|
|
|
|
|
taking too long, or are hanging or failing.
|
|
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
Make permanent with \fBNO_HTML_WAN='true'\fR
|
|
|
|
|
|
2018-03-26 01:42:49 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-man\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Disables man page install with \fB\-U\fR for master and active development
|
|
|
|
|
branches. (Only active if \fB\-U\fR is is not disabled by maintainers).
|
2018-03-26 01:42:49 +00:00
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-sensor\-force\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Overrides user set \fBSENSOR_FORCE\fR configuration value. Restores default
|
|
|
|
|
behavior.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
2018-03-24 09:18:41 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-ssl\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Skip SSL certificate checks for all downloader actions (\fB\-U\fR, \fB\-w\fR,
|
|
|
|
|
\fB\-W\fR, \fB\-i\fR). Use if your system does not have current SSL certificate
|
|
|
|
|
lists, or if you have problems making a connection for any reason. Works with
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
\fBWget\fR, \fBCurl\fR, \fBPerl HTTP::Tiny\fR and \fBFetch\fR.
|
2018-03-24 09:18:41 +00:00
|
|
|
|
New version, man page, exciting changes!!
Bugs:
1. issue #200 - forgot to add all variants for -p, now works with --partition-full
and --partitions-full
2. issue #199 - another one, forgot to add --disk to -D for long version. Thanks
adrian15 for both of these, he was testing something and discovered these were
missing.
3. Issue #187 an issue with RAID syntax not being handled in a certain case,
thanks EnochTheWise for following through on this one. This turned out to be
a bad copy paste, a test pattern did not match the match pattern.
Fixes:
1. Fixed some docs typos.
2. Issue #188 fixed protections and filters for some glxinfo output handlers.
3. Issue #195, for Elbrus bit detection.
4. Added filter to cpu data, was not skipping if arm, so Model string
was treated numerically.
Enhancements:
1. Added rescatux to Debian system base detections. This closes issue #202, again
from adrian15, thanks.
2. For cpu architecture, updated for latest AMD ryzen and other families, like
Zen 3, which is just coming out re available data. Also latest Intel, which are
trickier to ID right now, but I think I got the latest ones right,
That's things like coffee lake, amber lake, comet lake, etc.
3. Huge one, full (hopefully out of the box) Russian Elbrus CPU support. Thanks
to the alt-linux and the others who helped provide data and feedback to get support.
Note that this was also part of correcting 64 bit detection for e2k type, which
is how Elbrus IDs internally. See issue #197 which I've left open for the time
being for more information on this CPU and how it's now handled by inxi.
Note all available data should now work for Elbrus, including physical cpu/core
counts etc. Elbrus do not show flag information, nor do they use min/max speed,
so that data isn't available, but everything else seems to work well.
4. Eternal disk vendors. Thanks linux lite hardware database, you continue to
help make the disk vendor feature work by supplying every known vendor ever seen.
5. To close debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942194
Note that the fix is simply to give the user the option to disable this behavior
with the new --no-sudo and NO_SUDO configuration file options. This issue should
never have been filed as a bug since even the poster admitted it was a wishlist
item, but because of how debian bug tracker works, it's hard to get rid of
invalid bugs. Note that this is the internal use of sudo for hddtemp and file,
not starting inxi with sudo, so using this option or configuration item just
removes sudo from the command. Note that because the user did not do as
requested, and never actually filed a github wishlist issue, and since his
request was vague and basically pointless, the fix is just to let you switch
off sudo, that's all.
2019-11-20 04:42:21 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-no\-sudo\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Skips the use of sudo to run certain internal features (like \fBhddtemp\fR,
|
|
|
|
|
\fBfile\fR) with sudo. Not related to running inxi itself with sudo or
|
|
|
|
|
superuser. Some systems will register errors which will then trigger admin
|
|
|
|
|
emails in such cases, so if you want to disable regular user use of sudo (which
|
|
|
|
|
requires configuration to setup anyway for these options) just use this option,
|
|
|
|
|
or \fBNO_SUDO\fR configuration item.
|
New version, man page, exciting changes!!
Bugs:
1. issue #200 - forgot to add all variants for -p, now works with --partition-full
and --partitions-full
2. issue #199 - another one, forgot to add --disk to -D for long version. Thanks
adrian15 for both of these, he was testing something and discovered these were
missing.
3. Issue #187 an issue with RAID syntax not being handled in a certain case,
thanks EnochTheWise for following through on this one. This turned out to be
a bad copy paste, a test pattern did not match the match pattern.
Fixes:
1. Fixed some docs typos.
2. Issue #188 fixed protections and filters for some glxinfo output handlers.
3. Issue #195, for Elbrus bit detection.
4. Added filter to cpu data, was not skipping if arm, so Model string
was treated numerically.
Enhancements:
1. Added rescatux to Debian system base detections. This closes issue #202, again
from adrian15, thanks.
2. For cpu architecture, updated for latest AMD ryzen and other families, like
Zen 3, which is just coming out re available data. Also latest Intel, which are
trickier to ID right now, but I think I got the latest ones right,
That's things like coffee lake, amber lake, comet lake, etc.
3. Huge one, full (hopefully out of the box) Russian Elbrus CPU support. Thanks
to the alt-linux and the others who helped provide data and feedback to get support.
Note that this was also part of correcting 64 bit detection for e2k type, which
is how Elbrus IDs internally. See issue #197 which I've left open for the time
being for more information on this CPU and how it's now handled by inxi.
Note all available data should now work for Elbrus, including physical cpu/core
counts etc. Elbrus do not show flag information, nor do they use min/max speed,
so that data isn't available, but everything else seems to work well.
4. Eternal disk vendors. Thanks linux lite hardware database, you continue to
help make the disk vendor feature work by supplying every known vendor ever seen.
5. To close debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942194
Note that the fix is simply to give the user the option to disable this behavior
with the new --no-sudo and NO_SUDO configuration file options. This issue should
never have been filed as a bug since even the poster admitted it was a wishlist
item, but because of how debian bug tracker works, it's hard to get rid of
invalid bugs. Note that this is the internal use of sudo for hddtemp and file,
not starting inxi with sudo, so using this option or configuration item just
removes sudo from the command. Note that because the user did not do as
requested, and never actually filed a github wishlist issue, and since his
request was vague and basically pointless, the fix is just to let you switch
off sudo, that's all.
2019-11-20 04:42:21 +00:00
|
|
|
|
New version, new man, new feature!! Bug fixes!
Bugs:
1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it
was using unfiltered strings as regex pattern, and of course, a string flipped
an error. Fix was to add the regex cleaner to the string before it's used in test.
2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with
data or output so it couldn't be fixed. This was related to a syntax change in
usbdevs -v output in FreeBSD. Such changes are too common, but it might also
simply be a variant I have not seen or handled, but so far no data, so can't fix.
Don't blame me if you get this bug, but do post requested debugger data if you
want it fixed!
Fixes:
1. Updated man for weather, explained more clearly how to use country codes for
weather output. More clarifying in general about weather location, and weather
restrictions.
Enhancements:
1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from
liquorix for clarifying why that was a good idea. Note the initial issue came up
in a Debian issue report, not here. People!! please post issues here, and don't bug
maintainers with feature requests! Maintainers aren't in a position to add a feature,
so you should go straight to the source.
1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all
the flags, and also covers the short form flags and explains why they are used.
2. To resolve another issue, I made a new documentation file:
inxi-perl/docs/inxi-custom-recommends.txt
This is instructions for maintainers of distros who do not use rpm/apt/pacman but
still want the --recommends feature to output their package pool package names for
missing packages. I decided to not allow more than the default 3 package managers
because no matter what people say, if I allow in more, the maintainer will vanish
or lose interest, and I'll be stuck having to maintain their package lists forever.
Also, it's silly to even include that package list for any distro that does not
use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file
show what to change, and how, and has an example to make it clear. Odds of this
actually being used? Not high, lol, but that's fine, if people want it done, they
can do it, if not, nothing bad happens, it just won't show any suggested install
package, no big deal.
3. Using the new disk vendor method, added even more disk vendors. Thanks
linux litet hardware database!!
4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/
Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters,
from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me
where to look, I'll add it for those too, but wasn't anywhere I looked. Do the
BSDs even use that method? Don't know, but the logic is there, waiting to be used
if someone shows me how to get it cleanly. The 'parameters:' item shows in the main
'System:' -S output, and will just show the entire kernel parameters used to boot.
This could be very helpful to distros who often have to determine if for example
graphics blacklists are correctly applied for non free drivers, like nomodeset etc,
or if the opposite is present.
For forum/distro support, they just have to ask for: inxi -ba and they will see t
the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used
to trigger in this case the graphics and system lines.
5. Updated man/help for 4 as well, now explains what they will see with --admin/
-a options and -S. Good user suggestion, I wish all new features were this easy,
heh.
2019-05-01 00:56:10 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-pm\-type [package manager name]\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
For distro package maintainers only, and only for non apt, rpm, or pacman
|
|
|
|
|
based systems. To be used to test replacement package lists for recommends
|
|
|
|
|
for that package manager.
|
New version, new man, new feature!! Bug fixes!
Bugs:
1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it
was using unfiltered strings as regex pattern, and of course, a string flipped
an error. Fix was to add the regex cleaner to the string before it's used in test.
2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with
data or output so it couldn't be fixed. This was related to a syntax change in
usbdevs -v output in FreeBSD. Such changes are too common, but it might also
simply be a variant I have not seen or handled, but so far no data, so can't fix.
Don't blame me if you get this bug, but do post requested debugger data if you
want it fixed!
Fixes:
1. Updated man for weather, explained more clearly how to use country codes for
weather output. More clarifying in general about weather location, and weather
restrictions.
Enhancements:
1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from
liquorix for clarifying why that was a good idea. Note the initial issue came up
in a Debian issue report, not here. People!! please post issues here, and don't bug
maintainers with feature requests! Maintainers aren't in a position to add a feature,
so you should go straight to the source.
1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all
the flags, and also covers the short form flags and explains why they are used.
2. To resolve another issue, I made a new documentation file:
inxi-perl/docs/inxi-custom-recommends.txt
This is instructions for maintainers of distros who do not use rpm/apt/pacman but
still want the --recommends feature to output their package pool package names for
missing packages. I decided to not allow more than the default 3 package managers
because no matter what people say, if I allow in more, the maintainer will vanish
or lose interest, and I'll be stuck having to maintain their package lists forever.
Also, it's silly to even include that package list for any distro that does not
use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file
show what to change, and how, and has an example to make it clear. Odds of this
actually being used? Not high, lol, but that's fine, if people want it done, they
can do it, if not, nothing bad happens, it just won't show any suggested install
package, no big deal.
3. Using the new disk vendor method, added even more disk vendors. Thanks
linux litet hardware database!!
4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/
Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters,
from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me
where to look, I'll add it for those too, but wasn't anywhere I looked. Do the
BSDs even use that method? Don't know, but the logic is there, waiting to be used
if someone shows me how to get it cleanly. The 'parameters:' item shows in the main
'System:' -S output, and will just show the entire kernel parameters used to boot.
This could be very helpful to distros who often have to determine if for example
graphics blacklists are correctly applied for non free drivers, like nomodeset etc,
or if the opposite is present.
For forum/distro support, they just have to ask for: inxi -ba and they will see t
the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used
to trigger in this case the graphics and system lines.
5. Updated man/help for 4 as well, now explains what they will see with --admin/
-a options and -S. Good user suggestion, I wish all new features were this easy,
heh.
2019-05-01 00:56:10 +00:00
|
|
|
|
A small point release, some nice enhancements, a few bug fixes, and some fixes
to correct or update some issues. Main new features:
* -rx,-rxx,-ra/-Ix,-Ixx,-Ia: enhanced Packages: report
* -Cxx: microarchitecture level. This is a relatively new convention, used to
set various compile flags.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Can't safely look for pm tool KDE Discover because apt calls it
plasma-discover, but other packaging systems call it discover, which is already
a non-related program (hardware data). Since it's not really core to any package
manager, it's not really a necessary thing to report anyway, though
gnome-software is added because that appears to be more like syntaptic than
anything else.
There's also a qt variant of the rpm packagekit, packagekit-qt, which is
available in for example Arch, but again, it's too granular, and not really
core.
2. At some point, sensors should add /sys hwmon sensor data, then switch to
using lm-sensors as a fallback, and remove one recommended tool from newer linux
systems. I don't think that's too hard, just a bunch of little steps to
integrate that into the main logic.
--------------------------------------------------------------------------------
BUGS:
1. For Slackware slackpkg/pkgtool:
a: Failed to show package counts at all because of bad globbing path, forgot /*.
b. Failed to show lib counts for packages due to having wrong counter for path.
2. If no ipmi sensor data was found but the tools are present, could result in
an undefined hash reference error for sensors. The most likely cause for this is
that one of the ipmi commands:
"ipmi-tool sensors" or "ipmi-sensors"
had an error, and since errors are sent to /dev/null, inxi saw null data, then
returned an undefined value instead of the hash reference it was supposed to.
This is the first time I've seen this happen with ipmi, but there have not been
a lot of ipmi samples.
Thanks issue poster #274 for having systems that triggered this scenario.
3. $source for ipmi was set to lm-sensors by accident.
4. For sensors, with > 1 sensor type, like lm-sensors + ipmi, sensor data from
second sensor type was getting written to first sensor type row. See Fixes 9 for
more sensors fixes.
--------------------------------------------------------------------------------
FIXES:
1. Force CPU bits to 64 if LM flag is present, if it reports as i686. This fix
only runs for non RISC CPUs that show as 32 bit, so it won't run very often. If
no LM found, remains 32 bit.
This fix goes along with enhancement 1, which only applies to 64 bit CPUs.
2. In --recommends, JSON::PP module package names were wrong, they were copied
from JSON::Cpanel::XS and hadn't been changed to the right package names. Note
that for most distros, this is in Perl Core Modules, but not all.
3. Samsung ram vendor id was too tight, loosened it up a bit. Missed this one:
K3LK7K70BM
4. With Bug 1, extended possible package manager tool detection for slackware
type systems. Slackware is kind of unique in that it is not actually made out of
a core package manager as a collection of packages, but uses package managers as
a kind of layer on top of that, but none of those tools is required to run the
system.
5. Found another corner case indentation glitch, was adding in level 2 on -I
which is has no second level indentation.
6. Forgot to add $force{'pkg'} to -v8.
7. Small fix, if -Z is used, forgot to force --zl, --zu, --zv to false as well
as -z.
8. Small fix, for saphire rapids, alder lake, added + to year built, since those
are ongoing.
9. Sensors:
a. in one case, with an array of fan speeds, set to '' instead of undef, which
made test fail, and showed empty fan item.
b. added wildcards for possible voltage/power matches, was too restrictive for
ipmi sensors values.
c. added better space regex for ipmi temps [\s_-]?
d. DIMM voltage/temp excluded > 9 numbering, like DIMM 19
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: -Cxx shows for AMD / Intel 64 bit CPUs the microarchitecture
level (v1,v2,v3,v4). v1 is baseline. GCC supports this I believe in latest
versions, and some distros use it to determine CPU support levels for compile
time optimizations. This was introduced in 2020 via a collaboration between AMD,
Intel, SUSE, and Redhat. Now you know. This is a simple test based on which CPU
flags/features are present.
These levels can be used for Go language optimization (GOAMD64), GCC
optimization switches (GCC -O2 for example), and probably more.
2. Expanded YMTC (Yangtze Memory) RAM vendor ids and detections.
3. Added [unverified] window managers CDE and NsCDE. No data, only using ps aux
method.
4a. Added slax ID to distro id, added slax to system base support. Currently
only work on slackware based 15.0, not debian based 11.4.
4b. Added SteamOS debian/arch for system base.
4c. Added os-release VERSION_CODENAME to enhance distro ID data (eg steamos)
5. Added to -ra/-Ia package tools installed report, this goes along with change
2, which changes apt to dpkg, the low level tool. Now with -a, shows the package
manager tools installed, like slackpkg, apt, apt-get, dnf, yum, zypper, etc.
rpm installed as secondary pm requires some further tests. Currently known pm
that have tools (and rpm tests if detected):
All these are known to support rpm secondary pm:
* dpkg - Debian, Ubuntu, and apt-rpm based distros like PCLinuxOS, Alt Linux
* pacman - Arch based distros
* pkgtool - Slackware based distros
* tce - TinyCore Linux
6. A few more pci product IDs for GPU matches. Slow going.
--------------------------------------------------------------------------------
CHANGES:
1. Changed --pkg to --rpm, the original intention was that this could apply to
more than RPM package manager, but that's the only one that it's used for. This
leads to unclear output for other distributions where the user might have rpm
installed alongside their standard package manager.
2. Changed package pm: 'apt' to 'dpkg', to go along with type rpm (suse,redhat)
and pkgtool (slackware). Note that dpkg is the actual package manager of Debian,
inxi had this wrong, apt interacts with dpkg.
3. Changed -h -a section, to follow after -x, -xx, -xxx, like on man page.
4. For rpm notes, after running some tests to determine whether to use rpm or
not, will show the rpm note: see --rpm in pm: rpm note:... This allows for
more granular errors which will be more useful to users.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Docs were wrong for -ra/-Ia packages, from original when it package report
was only an -a option, but it got moved to -rx, -rxx for basic features, and -a
for advanced features.
2. Updated for --pkg/--rpm and --force rpm/pkg
3. See change 3, I think people tend to miss the sequence of -x, -xx, -xxx, -a
because -a came before -x, -xx, -xxx in -h menu, but on man page, -a correctly
comes after the -xxx options. Better to be consistent.
--------------------------------------------------------------------------------
CODE:
1. Switched force{pkg} to force{package} internally, and added converts to
change --force pkg/rpm to switch on $force{package}.
2. Refactored package PackageData to be more granular.
2022-08-23 00:55:45 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-rpm\fR, \fB\-\-pkg\fR
|
|
|
|
|
Shortcut. See \fB\-\-force rpm\fR.
|
|
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-sensors\-default\fR
|
|
|
|
|
Overrides configuration values \fBSENSORS_USE\fR or \fBSENSORS_EXCLUDE\fR
|
|
|
|
|
on a one time basis.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-sensors\-exclude\fR
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
Linux only. Similar to \fB\-\-sensors\-use\fR except removes listed sensors from
|
|
|
|
|
sensor data. Make permanent with \fBSENSORS_EXCLUDE\fR configuration item. Note
|
|
|
|
|
that gpu, network, disk, and other specific device monitor chips are excluded by
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
default.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
|
|
|
|
Example: \fBinxi \-sxx \-\-sensors\-exclude k10temp-pci-00c3\fR
|
|
|
|
|
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-sensors\-sys\fR
|
|
|
|
|
Shortcut. See \fB\-\-force sensors\-sys\fR
|
|
|
|
|
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-sensors\-use\fR
|
Another big one, with a long time to-do item done! /sys based sensors data is
now used as a fallback, with fully revised error messages to handle this new
sensor data variant. Due to potential bugs this might create, this was left off
of the 3.3.21 release, which needed to go out on a schedule, but there is plenty
of time for 3.3.22 to be debugged.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. inxi can't currently handle raw in[0-9] voltage sensor data from
/sys/class/hwmon, that may get corrected, but I've honestly never seen a system
that shows raw in[0-9] values as field names, so it's probably not very
pressing, but it can happen. Similar that is to how default fanx and tempx field
names are processed.
2. Currently only checking -Gx, -Nx device temp for bus IDs ending in .0, which
is the primary PCI device. I think that's the only one that will have a temp,
.1, which is a second device on the same hardware, doesn't have that data in
tests. Saves some requests since it's a big glob of /sys.
3. Spiral Linux has no obvious way to determine that it is Spiral and not Debian
11 as base distro. No /etc/ files for distro ID contain anything for spiral, so
leaving that one alone.
4. Can't get 100% reliable cpu level > v2 due to it not being a pure cpu flag
based test, which is kind of sadly typical for the originators of this idea, but
since the choice was dump the feature, or just use the note: check for > v2,
opted for note: check. One wants to ask questions here, but honestly I already
know the answer so why bother asking the question... The docs for this are
awful, inadequate, incomplete.
My strong suspicion is that this is NOT intended to be a distro-wide feature
beyond v2 support minimum, but rather is for specific compile options for a
package or daemon or server or whatever that can benefit from this type of
fine-tuning. One thinks of Gentoo for example back when such fine-tunings could
actually deliver noticeable differences in performance. A per system type
feature that is, not a distro-wide feature. At least that's my initial feeling,
but this is probably about all the time I will spend on it since inxi can't get
it more accurate anyway.
--------------------------------------------------------------------------------
BUGS:
1. Bug in monitor position logic, the horizontal/vertical sorts were being done
alphanumerically, leading to absurd results where 800 > 2560 or whatever.
Basically all x / y positions less than 1000 would have forced the smaller
number to be considered as the greatest value. Another corner case find by
mrmazda. Thanks mrmazda!
--------------------------------------------------------------------------------
FIXES:
1. Added i350bb sensor to network sensor type.
2. Small glitch with some scenarios with missing fan1 in sensors, showed fan1 0
rpm, but then showed fan 3: empty. That was a slight error in how undefined vs
'' empty was treated.
3. Added fix for defective fan speeds, skip fan item if > 15000, which is a bug
in the fan speed report, making it useless. Seen 65535 reported RPM. Could
probably make it 10000 upper limit but suspect that is a simple bug that creates
an absurd value, 2^16 so won't be anything high unless bug active. This fix runs
for ipmi, linux, and sysctl fan data.
4. Trying for fix for dynamic gpu voltage, assumed always mV, but might be V.
5. Inadequate or obscure or non-existent redhat/suse documentation led to some
fixes for cpu v levels. Note that level v3/v4 can't be fully determined by cpu
flag tests, but who cares? Certainly not me. Added 'note: check' for v3/v4.
6. Nvidia device arch id was too loose, false id for non existing lovelace arch.
Note that due to array reverse, the newest ids will always run first, which
leads to possible false positives with first string match tests when no product
IDs are available yet.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus CPU arch, process, year, arch data made more complete using new data
resource. Thanks Elbrus guys!
2. Finally, raw, basic /sys/class/hwmon temp data. Linux kernel docs note
supports temp, fan, volts, amps, energy. But have only seen temps so far. Can
force /sys use with --force sensors-sys / --sensors-sys, though there's no point
to doing that except to test.
Also changed --recommends to note lm-sensors not required for sensor data now.
3. Adding device temp for -Gx, -Nx. Will only work for Linux and when found, and
only for free drivers (I think).
4. Added xdriinfo based dri drivers (with fallback to Xorg.0.log as data source,
not as accurate), that will show if and only if that driver is not the same name
as a detected X or gpu driver.
5. Another big upgrade to cp_cpu_arch, added and corrected many AMD/Intel
matches.
6. A few more gpu product ids, Intel, added.
7. More disk vendors, ids, the list, as we are now well aware, is endless,
reflecting perhaps the futility of pursuing the infinite using finite means.
--------------------------------------------------------------------------------
CHANGES:
1. Slight changes in how inxi supplies no sensor data messages, and in the
fallback cases and handling. More accurate and precise, and more robust overall.
2. Due to complexity of understanding level: and the fact not all cpu flags are
exposed that are required, moved -Cxx level: to -Ca.
3. Changing slightly inaccurate Sound Server for ALSA/OSS to Sound API, which is
the closest I can come to explaining clearly what it is. Note that you can only
load one API type audio subsystem/driver, so you will be running one or the
other, never both, from what I understand.
Since OpenBSD sndio includes sndiod, calling that a sound server is basically
fine, since it's both the server and the interface, if I understand it right,
and there won't be a second sound server listed, actually won't be for any BSD
that I know of, it's going to be sndio or OSS or nothing, unless something has
changed.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Man page, updates for /sys/class/hwmon based sensor data.
2. Small update for cpu level v3/v4, added note: check explanation, though it's
too hard to really explain this stuff since the docs are... not wonderful, when
they even exist and don't contradict each other.
--------------------------------------------------------------------------------
CODE:
1. Refined significantly sensors missing data and error messages to be much more
accurate and granular. Also enables more sensors tools, though hopefully they
won't appear since those are a real pain to implement, but it's more open to
being sensor tool agnostic now due to these refinements than before.
2. Added xdpiinfo to debugger.
3. Switched x_drivers to return ref of array of refs, use join for output only,
that lets us use the drivers to test dri stuff also (if we want or need to), and
keeps it consistent with how most of inxi does that type of data
handling/testing. If undef, it means no array ref exists, which makes testing
easy.
Not truly understanding hash/array refs when inxi rewrite to Perl started is
probably one of the bigger causes of glitches and ongoing optimizations.
Basically, in all but very small array cases, it's almost always better to start
with a ref from the start as soon as the hash/array moves between functions,
with one exception, when it's a globally stored data item. Then it depends. But
this requires a consistent testing for null data as well, which is harder if you
did it in different ways from the start. But slowly and surely chipping away at
these.
2022-10-08 02:43:17 +00:00
|
|
|
Linux only. Use only the (comma separated) sensor arrays for \fB\-s\fR output.
|
|
|
|
|
Make permanent with \fBSENSORS_USE\fR configuration item. Sensor array ID value
|
|
|
|
|
must be the exact value shown in lm\-sensors sensors output (lm-sensors only) or
|
|
|
|
|
use \fB\-s \-\-dbg 18\fR ('main' =>.. section) to see the sensor ID strings used
|
|
|
|
|
internally. If you only want to exclude one (or more) sensors from the output,
|
2021-08-25 03:39:33 +00:00
|
|
|
use \fB\-\-sensors\-exclude\fR.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
|
|
|
|
|
Can be useful if the default sensor data used by inxi is not from the right
|
|
|
|
|
sensor array. Note that all other sensor data will be removed, which may lead
|
|
|
|
|
to undesired consequences. Please be aware that this can lead to many
|
|
|
|
|
undesirable side\-effects, since default behavior is to use all the sensors
|
|
|
|
|
arrays and select which values to use from them following a set sequence of
|
|
|
|
|
rules. So if you force one to be used, you may lose data that was used from
|
|
|
|
|
another one.
|
|
|
|
|
|
|
|
|
|
Most likely best use is when one (or two) of the sensor arrays has all the
|
|
|
|
|
sensor data you want, and you just want to make sure inxi doesn't use data
|
2021-08-25 03:39:33 +00:00
|
|
|
from another array that has inaccurate or misleading data.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
|
|
|
|
|
Note that gpu, network, disk, and other specific device monitor chips are
|
|
|
|
|
excluded by default, and should not be added since they do not provide cpu,
|
|
|
|
|
board, system, etc, sensor data.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
|
|
|
|
Example: \fBinxi \-sxx \-\-sensors\-use nct6791-isa-0290,k10temp-pci-00c3\fR
|
|
|
|
|
|
2017-11-29 01:28:28 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-sleep [0\-x.x]\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
Usually in decimals. Change CPU sleep time for \fB\-C\fR (current: \fB\0.35\fR).
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Sleep is used to let the system catch up and show a more accurate CPU use.
|
|
|
|
|
Example:
|
2018-04-06 22:52:08 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
\fBinxi \-Cxxx \-\-sleep 0.15\fR
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
Overrides default internal value and user configuration value:
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
|
|
|
|
\fBCPU_SLEEP=0.25\fR
|
|
|
|
|
|
2018-11-30 05:23:15 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-tty\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Forces internal IRC flag to off. Used in unhandled cases where the program
|
2021-08-25 03:39:33 +00:00
|
|
|
running inxi may not be seen as a shell/pty/tty, but it is not an IRC client.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Put \fB\-\-tty\fR first in option list to avoid unexpected errors. If you want
|
|
|
|
|
a specific output width, use the \fB\-\-width\fR option. If you want normal
|
2021-08-25 03:39:33 +00:00
|
|
|
color codes in the output, use the \fB\-c [color ID]\fR flag.
|
New version, new man page.
Bugs:
1. Both a fix and a bug, in that inxi had an out of date list of Xorg drivers.
This led to all the newer Intel devices failing to show their drivers in the
Xorg driver lines, like i915, i965, and so on. Updated to full current list of
Xorg drivers. This is not technically a bug since it's simply things that came
into existence after that logic was last updated. But it looks like a bug.
Fixes:
1. Issues #170 and #168 showed a problem with inxi believing it was running in IRC
when Ansible or MOTD started inxi. This is because they are not tty so trip the
non tty flag, which assumes it's in IRC in that case. The fix was to add a
whitelist of known clients based on the parent name inxi discovers while running
inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file
issue reports then not follow them? Who knows.
Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi
which disables the tty test as well. To handle that scenario, that is, when inxi is
not first in the pipe, I added many known terminal client names to the whitelists.
This works in my tests, though the possible terminals, or programs with embedded
terminals, is quite large, but inxi handles most of them automatically. When it
doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
in the meantime.
2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
in some character sets, like greek or russian utf8. The fix was more of a work-around
than a true fix, but inxi now simply checks the weather local time output for wide
characters, and if detected, switches the local date/time format to iso standard,
which is does not contain non ascii characters as far as I can tell. This seemed to
fix the issue.
3. Added iso9660 from excluded file systems for partitions, not sure how inxi
missed that one for so long.
4. See bug 1, expanded and made current supported intel drivers, and a few other
drivers, so now inxi has all the supported xorg drivers again. Updated docs as well
to indicate where to get that data.
Enhancements:
1. As usual, more disk vendor/product ID matches, thanks to linuxlite hardware
database, which never stops providing new or previously unseen disk ids. Latest
favorite? Swissarmy knife maker victorinox Swissflash usb device.
2. Added Elive system base ID.
3. Added Nutyx CARDS repo type.
2019-01-01 05:11:01 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
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
|
2023-09-18 00:42:36 +00:00
|
|
|
codeberg.org issue if you find you need to use \fB\-\-tty\fR (including the full
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fB\-Ixxx\fR line) so we can figure out how to add your program to the list of
|
|
|
|
|
whitelisted programs.
|
New version, new man page.
Bugs:
1. Both a fix and a bug, in that inxi had an out of date list of Xorg drivers.
This led to all the newer Intel devices failing to show their drivers in the
Xorg driver lines, like i915, i965, and so on. Updated to full current list of
Xorg drivers. This is not technically a bug since it's simply things that came
into existence after that logic was last updated. But it looks like a bug.
Fixes:
1. Issues #170 and #168 showed a problem with inxi believing it was running in IRC
when Ansible or MOTD started inxi. This is because they are not tty so trip the
non tty flag, which assumes it's in IRC in that case. The fix was to add a
whitelist of known clients based on the parent name inxi discovers while running
inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file
issue reports then not follow them? Who knows.
Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi
which disables the tty test as well. To handle that scenario, that is, when inxi is
not first in the pipe, I added many known terminal client names to the whitelists.
This works in my tests, though the possible terminals, or programs with embedded
terminals, is quite large, but inxi handles most of them automatically. When it
doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty
in the meantime.
2. Issue #171 by Vascom finally pinned down the wide character issue which manifests
in some character sets, like greek or russian utf8. The fix was more of a work-around
than a true fix, but inxi now simply checks the weather local time output for wide
characters, and if detected, switches the local date/time format to iso standard,
which is does not contain non ascii characters as far as I can tell. This seemed to
fix the issue.
3. Added iso9660 from excluded file systems for partitions, not sure how inxi
missed that one for so long.
4. See bug 1, expanded and made current supported intel drivers, and a few other
drivers, so now inxi has all the supported xorg drivers again. Updated docs as well
to indicate where to get that data.
Enhancements:
1. As usual, more disk vendor/product ID matches, thanks to linuxlite hardware
database, which never stops providing new or previously unseen disk ids. Latest
favorite? Swissarmy knife maker victorinox Swissflash usb device.
2. Added Elive system base ID.
3. Added Nutyx CARDS repo type.
2019-01-01 05:11:01 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
You can see what inxi believed started it in the \fB\-Ixxx\fR line,
|
|
|
|
|
\fBShell:\fR or \fBClient:\fR item. Please let us know what that result was
|
|
|
|
|
so we can add it to the parent start program whitelist.
|
2018-11-30 05:23:15 +00:00
|
|
|
|
Thanks manjaro user alven for finding a bunch of corner and not so corner case
errors, glitches, documentation oversights, etc.
This is a point release between the coming full CPU refactor and the current
set of bug fixes and issue handlings.
This release also contains the debuggers for the new CPU data logic, which are
important to get this CPU refactor stable and reliable across old/new systems,
different operating systems and platforms.
Wanted to do this intermediate releaase to get the current fixes out, which
make inxi overall better for CPU issues, but do not handle the core requirement
to do a full refactor.
--------------------------------------------------------------------------------
CORRECTION:
1. On release notes for 3.3.08: due to a long delay to get real debugger data
from the person who had the issue, but finally getting it after the release of
3.3.08, there was NO bug in ps wwaux output. Something else was creating the
linewraps, maybe the subshell, it's basically impossible to know since we never
got a real debugger data set, which is the only real way to get the actual same
data inxi will see.
Was it a subshell wrapping the output? We just can't know, nor are we likely to
ever find out.
This highlights very well however why some issues are essentially impossible to
ever fully resolve without the --debug 22 dataset. This bug/fix is definitely in
that class of issues.
It's never good to accuse another program of having a bug when it doesn't, so
sorry to ps authors, no bug or issue exists for ps in this area.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. wiryonolau issue #259 points out that if --tty is used, default IRC filter
rule is still active and on. Because his case appears to be from an autostart
using Bash, which then gives up to find the parent at dash, which then makes
inxi believe it's in an IRC shell client, that issue doesn't appear to be
resolvable.
--------------------------------------------------------------------------------
BUGS:
1. Documentation, help menu and man page showed wmctl instead of wmctrl,
which for someone who reads the help man, leads to command --fake wmctl failing.
Thanks manjaro user alven for finding this typo.
2. For dmidecode cpu data, had global total values for cache that could result
in wrong output values, 2x or more wrong for L1 / L3 cache on linux. Difficulty
is preserving that data for bsd, which in general do not show phys cpu counts,
and thus make showing totals off. Created new '-total' item for each L cache
type, which will handle > 1 cpus, and also can be used to determine if > 1 cpus
present!.
3. Manjaro user pointed out that hub types were wrong, this is because inxi was
using the INTERFACE ID values for hubs instead of the TYPE values. For all other
device types, INTERFACE is correct, but for hubs, we needed TYPE, so fix is to
detect INTERFACE 9/0/0 and if TYPE present for that, swap.
--------------------------------------------------------------------------------
FIXES:
1. For > 1 cpu systems, with dmidecode sourced cpu cache data, can now determine
physical cpu count based on comparing L2 and L2-total values. This means that
when dmidecode is used on BSD for CPU data, inxi may now be able to deduce that
it is a > 1 cpu system.
2. Forgot to set $run{'filter'} to 0 for whitelist start client detection.
3. Going along with bug 3, changed 'Full speed (or root) hub' to:
Full speed or root hub, to make more clear that it's one or the other, or both.
4. For apply_filter(), added test if <superuser required> just return the
string.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Going with bug 1, and fix 1, for > 1 cpu systems, will now show for all
cache: items L1: 2x 1.5 MiB (3 MiB), same for L2 and L3. This is far less
confusing than showing the totals without explaining what they are.
2. Going along with 1, now root is not required to show L1 and L3 -Cxx on Linux
as long as the system is reasonably new, about after 2008, and has getconf -a
supported. That support is came in somewhere around 2.10, not sure exactly when.
Debian Etch had it, Sarge did not, Ubuntu 9.10 had it. Tinycore does not have
getconf at all. This will probably be replaced by a more robust full cpu /sys
data tool.
3. Added ht to default short -Cx flag list, that should show, and it's short.
4. Added --no-filter to activate -Z, --filter-override isn't consistent with
other --no-xxx options, even I forgot it. No changes, just another way to use
-Z.
5. For issue #260 added pch as a new sensor output type, it's kind of a builtin
southbridge / northbridge in the CPU die, but it's not a core, and has a
different temp. Will anyone even know what pch is? probably not, but who cares.
--------------------------------------------------------------------------------
CHANGES:
1. No longer showing for > 1 physical cpu systems the sum total of L1/2/3 cache
data. Now shows per cpu L1/L2/L3, and if > 1 cpu, shows for example:
cache: L1: 2x 512 KiB (1024 KiB) L2: 2x 2 MiB (4 MiB) L3: 2x 20 MiB (40 MiB)
For single physical cpu output remains the same:
cache: L1: 576 KiB L2: 3 MiB L3: 16 MiB
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated help/man for L1/L3 cache -Cxx changes.
2. Updated man and help to suggest -Z for --tty.
3. Forgot to note -v 7 adds -f, added to man/help.
--------------------------------------------------------------------------------
CODE:
* Added 'getconf -a' to debugger, that may be usable for cpu cache data, need to
gather data on that to confirm. that's regading issue #257 cache glitches.
2. Removed all * $physical_count for cache data in cpu_properties, that is now
handled by creating string with cpu count, per cpu caches, and total in parens.
3. Added in fallback failure case for the ZFS file system issue exposed by
accident in issue #258 - will now log in debugger the error, so we can try to
find what is going on there, impossible to reproduce until we find what zfs or
more likely, freebsd, changed there. Could be hyper specific, some weird thing
like a person making a zfs device name with space, impossible to guess. Note
that since the freebsd user declined to supply any data to help resolve this
issue, then closed it, we're back where we usually end up with FreeBSD issues,
either a Linux user (or worse, me) willing and able to find the issue and supply
the debugger data required shows up, OR the issue is ignored as valid but
impossible to resolve.
RANT: Note that this also confirmed to me that in order to preserve my own
sanity and not waste endless hours trying to get data, from now on, unless
utterly trivial, if a FreeBSD user refuses to promptly supply the required data,
the issue will be closed with a freebsd-closed-no-data-supplied label, which
means, valid but not possible to solve due to user refusing to help me help
them.
Come on FreeBSD users!! If you want help, and inxi to support your distro, help
me help you!! If not, then why are you even filing an issue in the first place?
Do you expect faeries to spread magic bug / issue fixing faerie dust over inxi
and then activate it with their little wands? This is growing tiresome to be
honest because it's so utterly predictable.
4. Shuffled order of sensor type detections, there was a slim chance that a non
gpu sensor type could have string intel in it, so put the gpu sensors second
to last, before 'main'.
5. Started refactor of cpu core/cache logic. Added feature to cpu_arch, and
changed it to cpu_info since now it gives by vendor/family/model/stepping both
micorarch and cache/core math array returns. Also started refactor to make more
predictable, with increased comments, about what is going on in cpu_properties
to avoid breaking existing correct results.
6. Added to --debug /sys cpu data globber tool, that will help debugging the new
/sys cpu data feature, will let me insert the file data directly into the logic.
7. Added CpuItem::cpu_data_sys() with debuggers, that will now start collecting
user cpu data whenever the debugger is run, though it's not active yet.
8. Set $Data::Dumper::SortKeys = 1; dugh, could have saved big headaches if had
found this before. Makes all keys sorted cleanly, gets rid of random hash sorts.
2021-11-22 20:47:54 +00:00
|
|
|
In some cases, you may want to also use \fB\-\-no\-filter\fR/\fB\-Z\fR option if
|
|
|
|
|
you want to see filtered values. Filtering is turned on by default if \fBinxi\fR
|
|
|
|
|
believes it is running in an IRC client.
|
|
|
|
|
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-usb\-sys\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Shortcut. See \fB\-\-force usb\-sys\fR
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
|
2021-01-14 01:32:13 +00:00
|
|
|
.TP
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
.B \-\-usb\-tool\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Shortcut. See \fB\-\-force lsusb\fR
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-wan\-ip\-url [URL]\fR
|
|
|
|
|
Force \fB\-i\fR to use supplied URL as WAN IP source. Overrides dig or
|
|
|
|
|
default IP source urls. URL must start with http[s] or ftp.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
The IP address from the URL must be the last item on the last (non\-empty)
|
|
|
|
|
line of the page content source code.
|
2021-01-14 01:32:13 +00:00
|
|
|
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
Same as configuration value (example):
|
|
|
|
|
|
|
|
|
|
\fBWAN_IP_URL='https://mysite.com/ip.php'\fR
|
|
|
|
|
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-wayland\fR, \fB\-\-wl\fR
|
|
|
|
|
Shortcut. See \fB\-\-force wayland\fR.
|
|
|
|
|
|
New version, new man. Several bug fixes, enhancements, options.
Bugs:
1. In some cases, -S Desktop showed xfce when it wasn't xfce. This should be largely
corrected now.
2. Big bug: using lxqt-about for lxqt --version, now opens a dialog box, gui,
so removed that, and now checking lxqt-session for version info instead.
Fixes:
1. Now calling hitachi hgst drives vendor: HGST (Hitachi) to differentiate between
regular Hitachi and HGST hitachi. Added a few more disk vendors.
2. Distro base and core: added linuxlite, elementary. Some distros use:
/etc/upstream-release/lsb-release so testing for that and os-release now too.
3. Extended qt detections, may catch a few stray ones now in non kde qt
desktops.
4. Complete refactor of desktop, desktop info, wm, and -G compositor, now much
easier to extend each feature and add detections, move order around, etc.
Also moved wm to -Sxx now that I use fallback ps aux tests, which were themselves
also totally refactored and optimized. Fixed WindowMaker id, which is made more
annoying because they are the only upper/lower case program name, but in at least
debian, the actual program name is wmaker internally.
Also tightened in particular gnome-shell, which was failing to show due to too
restrictive filtering of desktop/vm repeats. Most wm do not contain the desktop
name in the string, gnome-shell does, only one I'm aware of.
5. Removed N/A from wmctrl output, which just means null, which is what we want.
6. Removed gnome-shell from info: since it will now appear in wm: if found. Added
a few -panel items to info:
Enhancements:
1. Showing type: network bridge for -N when it's type 0680, which is an odd pci
type, generally it's a network bridge, but I figured it's best to show that
explicitly to avoid confusion. This extends the 'type:' from just USB.
2. Added more window managers to wm, matchbox, flwm, fvwm2 (used to just use fvwm,
this was wrong, it's its own thing), a few others.
3. Added a few more compositors to -Gxx. kwin_x11 should be the most noticeable,
but added some more obscure ones too. This feature requires more work.
4. Extended ARM syntax to support a new one, path to /sys/device... has an extra
/soc/ in it, that is now handled, all are tested for. Confirmed working. Note that
ARM has to be confirmed fixed on a device by device basis, since there are key
syntax differences in the paths, but it will get easier the more variants that are
discovered. Added another trimmer to cut off \x00|01|02|03 special non printing
characters which show as weird jibbberish in output, for model/serial number.
5. Refactored wm, info, desktop, compositor, now all use @ps_gui, which is all that
is tested against, not the entire ps_cmd array. This drops the possible tests down
massively since the only things in ps_gui will be the actual stuff found that matches
all the patterns required for that system, not all ps items. Added marco, muffin
fixes. Was showing wm: Metacity (Marco) that is not correct, now shows marco, which
then allows to get version too.
5. -Sxxx now shows wm: version as well, which can be of use now and then.
6. --wm added to trip force using of ps data for wm, this can be useful because
I don't know all variants of wmctrl output, so that makes it easier to test.
7. Added finally support for --debug 3, which now shows timers, functions, and args
printed to screen.
8. Added qmake --version to fallback qt detection.
2018-07-08 23:30:15 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-wm\fR
|
Just as 3.3.10 > 3.3.11 were a huge set of CPU upgrades, including significant
internal refactors, so too is 3.3.13 a significant Graphics upgrade, featuring
significant upgrades to Wayland (and Xvesa/TinyX!) support, and allowing for
much more granular output controls. The legacy -Ga showing
Display/Screen/Monitors is now split apart, and can now work for some features
in and out of display.
This upgrade should be of significant interest to any Wayland using distro, as
well as the tiny Xvesa based distros like TinyCore, Slitaz, and Puppy.
--------------------------------------------------------------------------------
NOTE TO MAINTAINERS AND PACKAGERS:
If you had Cpanel::JSON::XS or JSON::XS Perl modules as dependencies, you can
remove those, inxi now can use JSON::PP, which is in Core Modules since Perl
5.14 (unless for some reason your distro removed that module from Core Modules).
Basically inxi will simply look for whichever of the 3 is installed, and use
that one.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. The free drivers for xorg like amdgpu, modesetting, alter the the internal
kernel IDs for monitors/gfx device ports, which is somewhat bizarre since the
ideal role of any ID is to be an identifier that always works. Due to this
situation, inxi has to map the kernel ids to the x driver monitor IDs in order
to show the advanced monitor data, like model: mapped: and modes:. This may not
always work as expected since if the mapping fails, the data will fail to match
to the monitors. While not enough data is in to make any conclusions, hoping
that this issue does not exist on Wayland compositors.
--------------------------------------------------------------------------------
BUGS:
1. Not sure if this was a bug, but I believe RAM vendor ID matches would never
have generated results, and might have generated errors. That's corrected as
part of Code fix 1.
--------------------------------------------------------------------------------
FIXES:
1. Tiny indentation level issue, for -Ga, Monitor was not set to be a container
for its data. This would only impact -y 1 or json and xml output cases, and would
be subtle, but it was an oversight.
2. Small fix for monitor dimensions, failed to switch the mm dimensions for
monitors placed in a vertical, portait mode, instead of standard landscape mode.
Now switches mm x and y if that is detected, which corrects dpi as well.
3. For Xvesa:
* Show vesa as display driver, Xvesa == vesa, dugh,lol.
* Show better Interface and Screen resolution data missing messages.
* See FIX 5 for adding in display-ID:.
* Show TinX Xvesa string for server data, not just Xvesa.
4. For Wayland, which currently has no EGL support in inxi, if no glxinfo
present, show EGL Wayland specific Messsage: for advanced EGL data, not the
generic glxinfo that were shown previously.
5. Display was relying on xdpyinfo or a Wayland environmental variable to set
display-ID:, now falls back always to $ENV{DISPLAY} if nothing else was found
and that exists. I hadn't realized how much was depending on those x tools,
which many people never had installed in the first place. This also supplies
that for Xvesa as well, which has features that need the Display-ID to use.
6. Intel family 6, model 17h, supposed to be yorkfield, was penryn, fixed.
7. Small fix for remove_duplicates, it was not case insensitive so missed things
like DELL Dell in strings.
8. Failed to detect or get Xfree86 X server version number.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Extensive Graphics Upgrades:
* -Gxx Devices: For some gpus / drivers, show vram total and used for -Gxx.
amdgpu supports this, I believe it's the only one, but don't know for sure.
* -Gxx Devices: (Linux only): Show active, off (connected but disabled, like a
closed laptop screen with attached moniitor), and empty ports on devices. Not
tested for USB yet.
* -Gxx Devices: Show device ports (like VGA-1, DVI-I-1, HDMI-A-1), active, off
(off is connected but disabled) and empty (linux only).
* -G Display/Screen: Removed strict dependency on xdpyinfo to show advanced xorg
screen and display data. Now it will show most of the data if xrandr is
available, and all if xrandr and xdpyinfo are installed. More granular error
messages as well.
* -G Wayland Display: new type, d-rect: for > 1 monitor Wayland display layouts.
Works roughly the same as Screen: s-res: does, except since Wayland has no
'Screen' concept, that goes into Display. This is sort of a rough algo,
basically it takes either the dimensions of the total of x and y resolutions, or
the greatest x or y resolution found for any monitor, whichever is greater, and
uses that to create the display rectangle resolution composite value.
* -G Display, Monitors: Extended display tool options from just xrandr to
swaymsg, wlr-xrandr, weston-info, wayland-info. Still nothing on kwin_wayland or
gnome-shell and mutter data.
*. -S, -G: compositors, full redo of list, now supported:
asc awc cage cagebreak cardboard chameleonwm clayland comfc dwc dwl epd-wm
fireplace feathers fenestra glass gamescope greenfield grefson hikari hopalong
inaban japokwm kiwmi kwinft labwc laikawm lipstick liri mahogany marina maze
motorcar newm nucleus orbital perceptia phoc pywm qtile river rustland simulavr
skylight sommelier sway swc swvkc tabby taiwins tinybox tinywl trinkster velox
vimway vivarium wavy waybox way-cooler wayfire wayhouse waymonad westeros
westford weston wio+ wio wxrc wxrd xuake
* -G Enhanced Interfaces/GL item, previously only type OpenGL forX, now has:
* X - OpenGL, requires glxinfo , same as before.
* Wayland - EGL, currently no tool available, stub in place. Allegedly this
data can be found but have no idea how or if a tool does that yet
* Xvesa - Interface: interface type (VBE/GOP). GOP not confirmed, no data
samples; v:, source:, dac: (no idea what it is, show it though), controller:,
and ram: items.
This is based on TinyX/Xvesa as found in TinyCore, but should work in Slitaz
and Puppy TinyX as well if those projects are still around.
* -G Display/Screen/Monitor data: Created structures and abstractions that allow
for Wayland/Xorg/Xvesa data, most new features will work with any of these. Or
Arcan, if that actually makes it, and we get data for it. We'll wait on Arcan,
heh.
* -G Display server: For Xvesa, added type TinyX to server if detected. Added
Xwayland, which was not handled previously. For Xwayland, if wayland running,
and if Xorg also installed, shows:
server: X.org
v: 1.20.14
with: Xwayland
v: 21.01
Otherwise shows:
server: Xwayland
v: 21.01
* -G Compositors: fixed a long standing weak spot, if > 1 compositor detected
running, not common, but could happen, shows all detected compositors.
Display: x11
server: X.Org
v: 1.20.13
compositors:
1: Mutter
v: 41.1
2: xfwm
v: 4.16.1
driver:
X:
loaded: modesetting
gpu: radeon
* -G drivers: now shows if X or gpu driver, in each its own section. This makes
it more obvious what is going on:
Display: x11
server: X.Org
v: 1.20.13
driver:
X:
loaded: modesetting
gpu: radeon
resolution:
* -Gxx Monitors: Show primary monitor with pos: primary,right. Uses either
xrandr 'primary' value, or if no 'primary' found in an Xorg Screen, uses +0+0
positioned monitor. Position is based on the row and column number in the
rectangular grid of monitors when monitors per Xorg Screen are > 1.
For most common multi-monitor layouts, text positions are used, which are in
general more clear and easy to understand than their internal numeric
counterparts, that is, unless the layout is too complicated, it will show left,
or top-left, instead of 1-1, and so on.
Text mode positions are available for the following grid styles currently: 1x2,
1x3, 1x4, 2x1, 2x2, 2x3, 3x1, 3x2, 3x3. 'top' means the top row if > 1 row,
'bottom' means the bottom row, 'middle' is the middle row if 3 rows, 'left' is
the first column, 'right' the last, 'center' if 3 columns, and 'center-l' (1-2),
'center-r' (1-3) are the 2 center columns if 4 columns. 'bottom-l', 'bottom-c',
'bottom-r'; 'middle-l', 'middle-c', 'middle-r'; 'top-left', 'top-center',
'top-right' complete the possible values.
If the grid of monitors is greater than the supported rows or columns, it will
switch to numeric row-column mode, with column-row numbering starting at 1-1,
top left.
* -Gxx Monitors: show (if detected, Linux only) monitor model, and if the
display ID (from Xorg or Wayland) is different from the /sys monitor ID, show
mapped: to show the /sys id.
* -Gxxx Monitors: show modes: max: XxY min: XxY, or mode: XxY (if only 1 mode
found). Shows hz:
* -Ga Monitors: shows serial, built year, gamma, ratio, if detected.
2. Added impish 21-10 and jammy 22-04 to ubuntu id. That's for Mint base ID. Not
huge point in updating if Mint doesn't update inxi, but there it is.
3. For -Axx, -Exx, -Gxx, -Nxx, shows PCIe speed and lanes. With -a, shows max
speed / lanes if different than current speeds/lanes. Note that for unknown
reasons not all devices in a PCIe slot show this data.
4. -Ixx: terminals added: foot, ate
5. -Sxx: login/display managers added: emptty, greetd, qingy, tbsm. See CODE 5
for more info on how this change was done.
6. -Sxxx: status/dock/panel bars added: i3-status-rs, luastatus, nwg-bar,
nwg-dock, nwg-panel, rootbar, sfwbar, wapanel, waybar, yambar
7. Added a Tyan board IPMI sensor data set.
8. Added support for fruid_print for Elbrus -M Machine data. Those boards don't
have dmi tables, but do ship with Elbrus OS which has fruid_print.
9. More disk vendors! Yes, you know the drill, the world turns, and with every
turn, a flock of new vendors appears, like baby rabbits emerging from their
warren, endlessly, a stream that is the life essence itself... or something.
--------------------------------------------------------------------------------
CHANGES:
1. When xdpyinfo is not installed, user will still see advanced -Ga Monitor and
Screen data as long as xrandr at least is installed. Better error messages as
well now to explain which tool or tools missing caused the missing data.
2. -Gxx will show basic Screen and Monitors, id, mapped, pos:, model, res, dpi,
diag; -Gxxx adds Monitor modes; --Ga adds screen/monitor size, Screen diag.
3. -ba/-v2 no longer show the full screens/monitor report, now it remains basic
mode output, which it should have always done, unless -G is also explicitly
added.
4. Split apart x-server version to v:, which should always have been the case.
5. Xvesa and Wayland no longer show glxinfo messages for no glxinfo for GL data.
Now they show their own custom messages, appropriate to the case.
6. json features now test for JSON::PP, JSON::XS, or Cpanel::JSON::XS modules,
and use whichever is found. Note I did not realize JSON::PP was in core modules
as of 5.14 so that makes sense to use, and will allow inxi to start using json
data sources, which are a lot easier to parse.
7. Changed -G drivers to show subsections for X and gpu drivers, and updated
missing driver messages to account for this change. X drivers now show the sub
sets of loaded/unloaded/failed/alternate, and gpu shows active gpu drivers,
assuming such are detected.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Help and man page updates for -G Display/Screen/Monitor changes. Redid -G,
-Gx, -Gxx, -Gxxx, -Ga. Added monitor layout position feature.
2. Updated -Ga for xrandr/xdpyinfo changes.
3. Updated --recommends to more accurately show function of xdpyinfo and xrandr
for -G and -Ga.
4. Reorganized and added complete table of contents to docs/inxi-data.txt
--------------------------------------------------------------------------------
CODE:
1. Slightly optimized use of array loads on disk_vendor() and ram_vendor() based
on how it's now done for monitor layouts, which is more efficient, use a scalar
to hold a reference to the array, that avoids having the array ever exist in
more than 1 place. Part of the ongoing process of avoiding extra hash and array
copies globally.
2. Moved to consistent undef behaviors.
* For lists of variables use () to undefine, changed all of the the following:
1. (@a,$b,$c,%d) = (undef,undef,undef,undef);
2. (@a,$b,$c,%d) = (undef);
3. (@a,$b,$c,%d) = undef;
to use: (@a,$b,$c,%d) = (); This undefines all the variables in the list.
Note that assigning undef to @a in the first example creates an array of 1
key, with the value undef, and (@a,@b) = (undef,undef) creates arrays of 2
indexes, or something like that. Not what was wanted.
Examples 2 and 3 assign undef to @a: an array of 1 index, value undef, and
undefine the others variables in the list. This was not the desired behavior!
* For most scalars, arrays, and hashes, use: undef @a; undef $s; undef %h.
* For some hash and array index values, use $h{a} = undef. These cases may want
the key itself to exist, with the value of undef, though I believe:
undef $h{a};
is synonymous, but still have to verify that.
I did some testing, and realized that some of the undef I had used in the
various previous ways of using undef were not actually resulting in the expected
behaviors.
3. Refactored display_data_x into 3 functions, added display_data_xdpyinfo and
display_data_xrandr, which allows for more granular handling of those
dependencies, now inxi can show most advanced display data with only xrandr
installed.
4. Significantly improved all error handling and missing data for Wayland/Xorg.
5. Refactored get_display_manager() to better handle corner case dm file or
directory names, and to avoid endless loops. Much cleaner now. Required because
greetd had varying file names, greetd.run, or just greet-546.sock. With some
other dm's that use similar, or unreadable directories in /run, now just doing
a glob of /run/ /var/run, /var/run/rc.d as detected and checking for the dms
in the names, then just using the dms that were found. Simpler.
6. Massively simplified and integrated compositor logic in Graphics, now using
program_values() and program_data() as appropriate, and simple matching list
to ps_gui data to get detected compositor[s], much simpler, far more efficient
code, less to maintain. Also fixed long-standing weak spot of exiting on first
detected compositor, now shows all detected, with version etc for each if
available.
7. With 6. also significantly simplified and optimized get_ps_de_data() for
desktop data, that's the ps aux fallback case for wm desktop detections.
8. Made $wl compositors list global to avoid having to update each section,
that's now used in -G compositor, -S desktop/wm, and wm sections. It is set
in ps_gui() on initial load.
7. Settled on one and only way to do multiline conditionals, now use no space,
use same indent level as starting if/elsif etc. I've been debating this one, but
can't find any real way to handle that elegantly so I think best to just not
try, and leave it up the code flow to show when it's wrapped condition tests.
8. Refactored previous gl_output, expanded it to handle all interface types,
OpenGL, EGL (not currently active due to no known tool to get EGL data for
Wayland, and Interface: VBE type data for Xvesa. This roughly completed the
breaking apart of the X.org centric logic for Display, Monitors, and GL data,
and make all sections now fully agnostic to display server or protocol type.
Should new display servers appear, it will now be far more simple to add support
for them, since they would just plug into the existing abstraction layers.
9. Added --debug-arg to allow for passing specific custom args to the debugger.
10. Refactored display_server version, now works much better, creates lists of
server/version, and xwayland as well if found.
2022-02-22 23:58:37 +00:00
|
|
|
Shortcut. See \fB\-\-force wmctl\fR.
|
New version, new man. Several bug fixes, enhancements, options.
Bugs:
1. In some cases, -S Desktop showed xfce when it wasn't xfce. This should be largely
corrected now.
2. Big bug: using lxqt-about for lxqt --version, now opens a dialog box, gui,
so removed that, and now checking lxqt-session for version info instead.
Fixes:
1. Now calling hitachi hgst drives vendor: HGST (Hitachi) to differentiate between
regular Hitachi and HGST hitachi. Added a few more disk vendors.
2. Distro base and core: added linuxlite, elementary. Some distros use:
/etc/upstream-release/lsb-release so testing for that and os-release now too.
3. Extended qt detections, may catch a few stray ones now in non kde qt
desktops.
4. Complete refactor of desktop, desktop info, wm, and -G compositor, now much
easier to extend each feature and add detections, move order around, etc.
Also moved wm to -Sxx now that I use fallback ps aux tests, which were themselves
also totally refactored and optimized. Fixed WindowMaker id, which is made more
annoying because they are the only upper/lower case program name, but in at least
debian, the actual program name is wmaker internally.
Also tightened in particular gnome-shell, which was failing to show due to too
restrictive filtering of desktop/vm repeats. Most wm do not contain the desktop
name in the string, gnome-shell does, only one I'm aware of.
5. Removed N/A from wmctrl output, which just means null, which is what we want.
6. Removed gnome-shell from info: since it will now appear in wm: if found. Added
a few -panel items to info:
Enhancements:
1. Showing type: network bridge for -N when it's type 0680, which is an odd pci
type, generally it's a network bridge, but I figured it's best to show that
explicitly to avoid confusion. This extends the 'type:' from just USB.
2. Added more window managers to wm, matchbox, flwm, fvwm2 (used to just use fvwm,
this was wrong, it's its own thing), a few others.
3. Added a few more compositors to -Gxx. kwin_x11 should be the most noticeable,
but added some more obscure ones too. This feature requires more work.
4. Extended ARM syntax to support a new one, path to /sys/device... has an extra
/soc/ in it, that is now handled, all are tested for. Confirmed working. Note that
ARM has to be confirmed fixed on a device by device basis, since there are key
syntax differences in the paths, but it will get easier the more variants that are
discovered. Added another trimmer to cut off \x00|01|02|03 special non printing
characters which show as weird jibbberish in output, for model/serial number.
5. Refactored wm, info, desktop, compositor, now all use @ps_gui, which is all that
is tested against, not the entire ps_cmd array. This drops the possible tests down
massively since the only things in ps_gui will be the actual stuff found that matches
all the patterns required for that system, not all ps items. Added marco, muffin
fixes. Was showing wm: Metacity (Marco) that is not correct, now shows marco, which
then allows to get version too.
5. -Sxxx now shows wm: version as well, which can be of use now and then.
6. --wm added to trip force using of ps data for wm, this can be useful because
I don't know all variants of wmctrl output, so that makes it easier to test.
7. Added finally support for --debug 3, which now shows timers, functions, and args
printed to screen.
8. Added qmake --version to fallback qt detection.
2018-07-08 23:30:15 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH DEBUGGING OPTIONS
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
.TP
|
A nice release, some good corner case bug and glitch fixes, along with some much
needed documentation fixes to bring inxi-values.txt up to date for changes that
have been evolving steadily. And a useful option for nvidia legacy card info.
I'm hoping that will help support people and users as nvidia open source driver
gets more usable in the future, since that will never support legacy cards, only
the current series supported by 510/515 drivers.
Also, in inxi-perl/tools, new tools and data so you can reproduce certain arcane
data assembly features like disk vendors and nvidia product ids.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Not known yet if you can get Wayland display drivers along with kernel gpu
drivers. In other words, is a similar use of kernel/display driver as in Xorg
found with Wayland? Hard to dig up actual answers to questions like this.
2. Similarly, unknown if it's possible to get current active xorg display
driver, not just the list from Xorg.0.log file. No idea how to discover that,
there are cases where past use of Xorg leaves log file present, but drivers are
not used with Wayland, leading to confusing driver reports. Issues 1 and 2 are
similar but probably have similar solutions.
--------------------------------------------------------------------------------
BUGS:
1. Very subtle failure caused by odd mount point in partitions: a too loose
regex rule designed to capture spaces in device names was running loose to the
end of the string, where it was triggered by a number in the mount point.
Fix was to make rule much more strict, now needs to match 3 number space in a
row after the initial part, and then a number%
2. Bug in corner case, with Monitors, if > 2 connected monitors, and 1 disabled,
inxi was trying to test numeric position values for the disabled monitor, which
with xrandr, has no position values, thus tripping undefined pos-x and pos-y
errors. Thanks to fourtysixandtwo for spotting this corner case.
3. Bug in wan IP, if dig failed, set_dowloader() is not set unless other
parameters were used, which results in failing to set parameters for downloader,
which leads to screen errors spraying out. Thanks to Manjaro user exaveal for
posting this issue, with error outputs, which helped pinpoint the cause.
--------------------------------------------------------------------------------
FIXES:
1. More absurd xorg port ID variations: DP-1 kernel, DP1-1 X driver. Wny?
Trying to add in XX-?\d+-\d+ variation, which I think will be safe, made the
first - optional, though it's just idiotic for this amount of randomness to be
allowed to exist in the 21st century. If this reflects other discipline failures
in Xorg, it starts to get somewhat more obvious why Wayland was considered as
the only forward path, though that's just as chaotic and disorganized... but in
different ways.
2. Removed darwin distro version detection, which of course broke, and using
standard fallback for BSD made out of uname array bits. If it works, it works,
if not, who cares. This should handle issue #267 hopefully.
3. Trying for more monitor matches, now in cases where 1 monitor display ID
remained unmatched, and 1 sys kms id remains unused, assume the remaining
nonitor ID is a match and overwrite the unmatched message for that ID. This
will cover basically all single monitor match failure cases, and many multi
monitor failures with only 1 out of x monitor ids unmatched. While guessing a
bit, it's not a bad guess, and will slightly expand the number of matched
monitor ids. This extends the previous guess where if single monitor and
unmatched, use it to cover > 1 monitors, with 1 unmatched.
4. LINES_MAX configuration item did not assign to right variable when -1 value.
Used non-existing $size{'output-block'} instead of correct $use{'output-block'}
5. Forgot to add pkg to --force, goes with --pkg.
6. Finally! Added in busybox shell detection, it's not of course reliable if
they change internal light shells, but all the docs say they use ash, so now
it will show shell: ash (busybox) to make it clear. Hurray!! This means that
tinycore users will get this long awaited feature! Ok, ok, long awaited by
probably only me, but since I package inxi for busybox, it was on my todo list.
7. Cleaned up and re-organized many disk vendor matching rules, made them easier
to read and debug, going along with Code 3, vendors.pl development and release.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New feature: in -Ga, if Nvidia card, shows last supported nvidia legacy
series driver (like 304.xx), status, microarch. If --nvidia and EOL, shows
last-supported: kernel: xorg: info. This should be useful for support people,
we'll see.
-Gx shows nvidia microarchitecture, if it was found. This is based on matching
tables so will go out of date if you have non current inxi's, but that's life.
If --nvidia or --nv shortcut is used instead, triggers -Ga and shows much more
nvidia driver data for legacy, and for EOL drivers, last supported kernel, xorg,
and last release version. --nvidia also adds process node if available.
More important perhaps is the fact that as of May 2022, nvidia is starting the
process of open sourcing its current latest driver (515, but Turning, Ampere
architectures only so far), which will only support non legacy nvidia cards,
making detection of legacy cards even more important to support people and end
users, since that will be a common question support people will have: does my
card support the open source driver?"
Read about the new open sourcing of the 515 nvidia module:
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
https://github.com/NVIDIA/open-gpu-kernel-modules
https://www.phoronix.com/scan.php?page=article&item=nvidia-open-kernel&num=1
2. Going along with new and upgraded tools in Code 3, massive, huge, upgrade to
disk vendors, 100s of new matches, biggest upgrade ever for disk vendors. This
feature should work much better now with the new backend tools.
3. Added shortcuts: --mm for --memory-modules, --ms for --memory-short.
--------------------------------------------------------------------------------
CHANGES:
1. None.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Big update to docs/inxi-values.txt. This had gotten really out of date, with
incorrect hash and other internal data assignments, all updated to be current,
along with sample greps to make it easier to locate changes in the future as
well. This makes this document fairly up to date and useful again for dev
reference purposes, should such a dev ever appear, lol. Many values had not
been updated after global refactors, like switching to the %risk data for all
arm/mips/ppc platform types, and making %load, %use, %force, %fake uses more
consistent. Doing this helped expose some subtle bugs and failure cases in
inxi as well.
2. Added to -h and man -Ga Nvidia option info. Fixed some typos and glitches.
Includes new --nvidia / --nv options for full data.
--------------------------------------------------------------------------------
CODE:
1. Changed $dl{'no-ssl-opt'} to $use{'no-ssl'} and $dl{'no-ssl'}, that was a
confusing inconsistency.
2. Added comma separated list of --dbg numbers, since often > 1 is used. Saves
some debugging time, otherwise nothing changes.
3. Huge new public release of some back end tools in new section:
inxi-perl/tools
* vendors.pl - disk vendors tool, with data in lists/disks*.txt
* ids.pl - nvidia product id generator tool, with data in lists/nv_*
4. While doing vendors.pl, I noticed that the use of array ref for $vendors was
not done correctly, that's fixed now, simplifies it slightly.
2022-05-19 21:17:33 +00:00
|
|
|
.B \-\-dbg {[1\-x][,[1\-x]]}\fR
|
|
|
|
|
Accepts one or more comma separated dbg specific debugging numbers.
|
|
|
|
|
|
|
|
|
|
\fB1\fR \- Debug downloader failures. Turns off silent/quiet mode for curl, wget,
|
|
|
|
|
and fetch. Shows more downloader action information. Shows some more information
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
for Perl downloader.
|
|
|
|
|
|
2023-09-18 00:42:36 +00:00
|
|
|
\fB1\-xx\fR \- See codeberg.org \fBinxi\-perl/docs/inxi\-values.txt\fR for
|
|
|
|
|
specific specialized debugging options. There are a lot.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug [1\-3]\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\- On screen debugger output.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug 10\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
\- Basic logging. Check \fB$XDG_DATA_HOME/inxi/inxi.log\fR or
|
2018-04-04 06:41:06 +00:00
|
|
|
\fB$HOME/.local/share/inxi/inxi.log\fR or \fB$HOME/.inxi/inxi.log\fR.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug 11\fR
|
2018-04-04 06:41:06 +00:00
|
|
|
\- Full file/system info logging.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug 20\fR
|
2018-04-04 06:41:06 +00:00
|
|
|
Creates a tar.gz file of system data and collects the inxi output
|
|
|
|
|
in a file.
|
2014-04-03 18:35:14 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
* tree traversal data file(s) read from \fB/proc\fR and \fB/sys\fR, and
|
|
|
|
|
other system data.
|
2014-04-03 18:35:14 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
* xorg conf and log data, xrandr, xprop, xdpyinfo, glxinfo etc.
|
|
|
|
|
|
|
|
|
|
* data from dev, disks, partitions, etc.
|
2014-04-03 18:35:14 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug 21\fR
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
Automatically uploads debugger data tar.gz file to \fIftp.smxi.org\fR,
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
then removes the debug data directory, but leaves the debug tar.gz file.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
See \fB\-\-ftp\fR for uploading to alternate locations.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-debug 22\fR
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
Automatically uploads debugger data tar.gz file to \fIftp.smxi.org\fR, then
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
removes the debug data directory and the tar.gz file.
|
|
|
|
|
See \fB\-\-ftp\fR for uploading to alternate locations.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-id [string]\fR
|
|
|
|
|
Insert string to file name for debugger. This is helpful so you can add for
|
|
|
|
|
instance a username to a debugger dataset to make it easy to find.
|
|
|
|
|
|
|
|
|
|
Sample: \fB\-\-debug 22 \-\-debug\-id mrmazda\fR
|
|
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-fake\-data\-dir\fR
|
|
|
|
|
Developer only: Change default location of $fake_data_dir, which is where files
|
|
|
|
|
are for \fB\-\-fake {item}\fR items.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.B \-\-ftp [ftp.yoursite.com/incoming]\fR
|
2018-04-06 22:52:08 +00:00
|
|
|
For alternate ftp upload locations: Example:
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
|
|
|
|
\fBinxi \-\-ftp \fIftp.yourserver.com/incoming\fB \-\-debug 21\fR
|
|
|
|
|
|
New version, new man.
Bugs:
1. If you consider failure to identify a mounted yet hidden partition a bug, then
that bug is fixed, but I consider that as more of a fix than a bug.
Fixes:
1. Added more device pattern ID for odroid C1 and C2, these are now pretty well
supported.
2. inxi failed to handle a certain type of hidden partition, so far only seen
with udiskctl mounted TimeShift partitions, but this may be a more general udisk
issue, but so far not enough information. The fix is to use the lsblk data to
build up missing partitions, so this fix is for non legacy Linux systems only.
The fix works pretty well, but it's hard to know until we get a lot more real
world data, but given so far I've received only one issue report on it, I
suspect this is not a common situation, but you never know, it would never
have shown up in datasets unless I had looked specifically for it, so it may
be more common than I think.
3. Cleaned up and simplified new --admin -p and -d logic.
Enhancements:
1. For debugging, renamed all user debugger switches to have prefix --debug.
These options are to help debug debugger failures, and so far have been tested
and solved the failures, so I'm adding them all to the main man and help menu,
thus raising them to the level of supported tools. These were enormously helpful
in solving proc or sys debugger hangs.
* --debug-proc
* --debug-proc-print
* --debug-no-sys
* --debug-sys
* --debug-sys-print
2. Added findmnt output to debugger, that may be useful in the future. Also added
df -kTPa to also catch hidden partitions in debugger.
3. Added in another user level debugger, triggered with --debug-test-1 flag. This
will do whatever operation is needed at the time for that user. Some issues can
only be resolved by the user on their machine.
4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!
2018-09-28 21:25:17 +00:00
|
|
|
.SH DEBUGGING OPTIONS TO DEBUG DEBUGGER FAILURES
|
Huge upgrade, major rewrite/refactor, new features, everything is polished!!!
Note that due to large number of internal changes to code, a separate
INTERNAL CODE CHANGES section is at the bottom. Those are changes which in
general do not impact what users see that much, but which definitely impact
working on and with inxi! They also make errors less likely, and removed many
possible bad data error situations.
BUGS:
1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd
never gotten a dataset for before, this tripped a series of errors in inxi, which
were actually caused by small errors and failures to check certain things, as
well as simply never assigning data in corner cases. This system used only dmi
handles 6 and 7, which is a very rare setup, from the very early days of dmi
data being settled, but it was valid data, and actually inxi was supposed to support
it, because I'd never gotten a dataset containing such legacy hardware data, the
support didn't work. There were actually several bugs discovered while tracking
this down, all were corrected.
2. Going along with the cpu fixes below, there was a bug that if stepping was 0,
stepping would not show. I had not realized stepping could be 0, so did a true/false
test instead of a defined test, which makes 0 in perl always test as false. This is
corrected.
3. While going through code, discovered that missing second argument to main::grabber
would have made glabel tool (BSD I think mostly) always fail, without exception.
That explains why bsd systems were never getting glabel data, heh.
4. Many null get_size tests would not have worked because they were testing
for null array but ('','') was actually being returned, which is not a null array.
The testing and results for get_size were quite random, now hey are all the same
and consistent, and confirmed correct.
5. In unmounted devices, the match sent to @lsblk to get extended device data
would never work with dm-xx type names, failed to translate them to their
mapped name, which is what is used in lsblk matches, this is corrected.
This could lead to failures to match fs of members of luks, raid, etc,
particularly noticeable with complex logical device structures. This means
the fallback filters against internal logic volume names, various file system
type matches, would always fail.
6. A small host of further bugs found and fixed during the major refactor, but
not all of them were noted, they were just fixed, sorry, those will be lost
to history unless you compare with diffs the two versions, but that's thousands
of lines, but there were more bugs fixed than listed above, just can't remember
them all.
FIXES:
1. There was some ambiguity about when inxi falls back to showing hardware graphics
driver instead of xorg gfx driver when it can't find an xorg driver. That can happen
for instance because of wayland, or because of obscure xorg drivers not yet supported.
Now the message is very clear, it says the gfx software driver is n/a, and that it's
showing the hardware gfx driver.
2. Big redo of cpu microarch, finally handled cases where same stepping/model ID
has two micorarches listed, now that is shown clearly to users, like AMD Zen family
17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and
a comment: note: check, like it shows for ram report when it's not sure. Shows
for instance:
arch: Zen/Zen+ note: check
in such cases, in other words, it tells users that the naming convention
basically changed during the same hardware/die cycle.
3. There were some raid component errors in the unmounted tests which is supposed
to test the raid components and remove them from the mounted list. Note that inxi
now also tests better if something is a raid component, or an lvm component, or
various other things, so unmounted will be right more often now, though it's still
not perfect since there are still more unhandled logical storage components that
will show as unmounted when tney are parts of logical volumes. Bit by bit!!
4. Part of a significant android fine tuning and fix series, for -P, android uses
different default names for partitions, so none showed, now a subset of standard
android partitions, like /System, /firmware, etc, shows. Android will never work
well though because google keeps locking down key file read/search permissions in
/sys and /proc.
5. More ARM device detections, that got tuned quite a bit and cleaned up, for
instance, it was doing case sensitive checks, but found cases where the value
is all upper case, so it was missing it. Now it does case sensitive device type
searches.
6. One of the oldest glitches in inxi was the failure to take the size of the raid
arrays versus the size totals of the raid array components led to Local Storage
results that were uselessly wrong, being based on what is now called 'raw' disk
totals, that's the raw physical total of all system disks. Now if raid is detected
the old total: used:... is expanded to: total: raw:... usable:....used:, the usable
being the actual disk space that can be used to store data. Also in the case of
LVM systems, a further item is added, lvm-free: to report the unused but available
volume group space, that is, space not currently taken by logical volumes. This
can provide a useful overview of your system storage, and is much improved over
the previous version, which was technically unable to solve that issue because
the internal structures did not support it, now they do. LVM data requires sudo/
root unfortunately, so you will see different disk raw totals depending on
if it's root or not if there is LVM RAID running.
Sample: inxi -D
Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB
lvm-free: 84.61 GiB used: 8.49 GiB (3.1%)
lvm-free is non assigned volume group size, that is, size not assigned
to a logical volume in the volume group, but available in the volume group.
raw: is the total of all detected block devices, usable is how much of that
can be used in file systems, that is, raid is > 1 devices, but those devices
are not available for storage, only the total of the raid volume is.
Note that if you are not using LVM, you will never see lvm-free:.
7. An anonymous user sent a dataset that contained a reasonable alternate
syntax for sensors output, that made inxi fail to get the sensors data. That was
prepending 'T' to temp items, and 'F' to fan items, which made enough sense though
I'd never seen it before, so inxi now supports that alternate sensors temp/fan
syntax, so that should expand the systems it supports by default out of the box.
8. Finally was able to resolve a long standing issue of loading File::Find, which
is only used in --debug 20-22 debugger, from top of inxi to require load in the
debugger. I'd tried to fix this before, but failed, the problem is that redhat
/fedora have broken apart Perl core modules, and made some of them into external
modules, which made inxi fail to start due to missing use of required module that
was not really required. Thanks to mrmazda for pointing this out to me, I'd tried
to get this working before but failed, but this time I figured out how to recode
some of the uses of File::Find so it would work when loaded without the package
debugger, hard to figure it, turned out a specific sub routine call in that
specific case required the parentheses that had been left off, very subtle.
9. Subtle issue, unlike most of the other device data processors, the USB
data parser did not use the remove duplicates tool, which led in some cases
to duplicated company names in the output for USB, which looks silly.
10. Somehow devtmpfs was not being detected in all cases to remove that from
partitions report, that was added to the file systen filters to make sure it
gets caught.
11. Removed LVM image/meta/data data slices from unmounted report, those are LVM
items, but they are internal LVM volumes, not available or usable. I believe
there are other data/meta type variants for different LVM features but I have
added as many types as I could find.. Also explictly now remove any _member type
item, which is always part of some other logical structure, like RAID or
LVM, those were not explicitly handled before.
12. Corrected the varous terms ZFS can use for spare drives, and due to how
those describe slightly different situations than simply spare, changed the spare
section header to Available, which is more accureate for ZFS.
ENHANCEMENTS:
1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/
model/stepping IDs (E8C2), so that is fairly up to date now.
2. Added in a very crude and highly unreliable default fallback for intel:
/sys/devices/cpu/caps/pmu_name which will show the basic internal name used
which can be quite different from what the actual microarch name is, but the hope
is that for new intel cpus that come out after these last inxi updates, something
may show, instead of nothing. Note these names are often much more generic, like
using skylake for many different microarches.
3. More android enhancements, for androids that allow reading of /system/build.prop,
which is a very useful informative system info file, more android data will show,
like the device name and variant, and a few other specialized items. You can see if
your android device lets inxi read build.prop if you see under -S Distro:
Android 7.1 (2016-07-23) or just Android. If it shows just android, that means
it can't read that file. Showing Android however is also new, since while inxi
can't always read build.prop if that file is there, it's android, so inxi
finally can recognize it's in android, even though it can't give much info if
it's locked down. Inxi in fact did not previously know it was running in android,
which is quite different from ARM systems in some ways, but now it does.
If the data is available, it will be used in Distro: and in Machine: data to add
more information about the android version and device.
4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just
the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID,
Logical reports. Note that /dev/mapper/ is removed from the mapped name since
that's redundant and verbose and makes the output harder to read. For mapped
devices, the new --logical / -L report lets you drill into the devices to find
out what dm-xx is actually based on, though that is a limited feature which only
supports drilling to a depth of 2 components/devices, there can be more,
particularly for bcache, luks setups, but it's just too hard to code that
level of depth, so something is better than nothing in this case, which
is the actual choice I was faced, the perfect in this case really is/was
the enemy of the good, as they say.
5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number,
which again lets you trace each device around the system and report.
6. Added mdadm if root for mdraid report, that let me add a few other
details for mdraid not previously available. This added item 'state;'
to the mdraid report with right -x options.
7. Added vpu component type to ARM gfx device type detection, don't know
how video processing vcu had escaped my notice.
8. Added fio[a-z] block device, I'd never heard of that before, but saw
use of it in dataset, so learned it's real, but was never handled as a
valid block device type before, like sda, hda, vda, nvme, mmcblk,
etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number.
9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note
that in their nomenclature, L0 and L1 are actually both L1, so add those
together when detected.
10. RAM, thanks to a Mint user, antikythera, learned, and handled something
new, module 'speed:' vs module 'configured clock speed:'.
To quote from supermicro:
<<<
Question: Under dmidecode, my 'Configured Clock Speed' is lower than my
'Speed'. What does each term mean and why are they not the same?
Answer: Under dmidecode, Speed is the expected speed of the memory
(what is advertised on the memory spec sheet) and Configured Clock Speed
is what the actual speed is now. The cause could be many things but the
main possibilities are mismatching memory and using a CPU that doesn't
support your expected memory clock speed.
Please use only one type of memory and make sure that your CPU supports
your memory.
>>>
11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported
in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This
will let users make apples to apples speed comparisons between different systems.
Since MT/S is largely standard now, there's no need to translate that to MHz.
12. And, even more!! When RAM speeds are logically absurd, adds in note: check
This is from a real user's data by the way, as you can see, it triggers all
the new RAM per Device report features.
Sample:
Memory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
Array-1: capacity: N/A slots: 4 note: check EC: N/A
Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 61910 MT/s (30955 MHz) note: check
Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
actual: 2 MT/s (1 MHz) note: check
13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity
exists, here, now, and manifests every day!! Thanks to linux-lite hardware
database for this eternally generating list. Never underestimate the
creativity of mankind to make more disk drive companies, and to release
new model IDs for existing companies. Yes, I feel that this is a metaphore
for something much larger, but what that is, I'm not entirely clear about.
CHANGES:
1. Recent kernel changes have added a lot more sensor data in /sys, although
this varies system to system, but now, if your system supports it, you can
get at least partial hdd temp reports without needing hddtemp or root. Early
results suggest that nvme may have better support than spinning disks, but it
really varies. inxi will now look for the /sys based temp first, then fall
back to the much slower and root / sudo only hddtemp. You can force hddtemp
always with --hddtemp option, which has a corresponding configuration item.
2. The long requested and awaited yet arcane and obscure feature -L/--logical,
which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well
as handling LVM raid, both regular and thin, is now working, more or less.
This took a lot of testing and will probably not be reasonably complete for
a while, mainly because the levels of abstraction possible between lvm,
lvm raid, mdraid, LUKS, bcache, and other caching and other encryption
options are just too deep to allow for easy handling, or easy outputs.
But a very solid and good start in my view, going from nothing to something
is always a big improvement!! LVM reports require root/sudo. This will,
finally, close issue #135.
3. Going along with -L, and serving as a model for the logic of -L, was the
complete refactor of -R, RAID, which was a real mess internally, definitely
one of the messiest and hardest to work with features of inxi before the
refactor. It's now completely cleaned up and modularized, and is easy to add
raid types, which was not possible before, now it cleanly supports zfs, mdraid,
and lvm raid, with in depth reports and added items like mdraid size, raid
component device sizes and maj:min numbers if the -a option is used. Note
that LVM RAID requires root/sudo.
4. Added some more sensors dimm, volts items, slight expansion. Note that the
possible expansion of sensors made possible by the recently upgraded sensors
output logic, as well as the new inxi internal sensors data structure,
which is far more granular than the previous version, and allows for much
more fine grained control and output, though only gpu data currently takes
advantage of this new power under the covers, although as noted, the /sys based
hdd temps use the same source, only straight from /sys, since it was actually
easier using the data directly from sys than trying to map the drive locations to
specific drives in sensors output. Well, to be accurate, since now only
board type sensors are used for the temp/fan speed, voltage, etc, reports,
the removal of entire sensor groups means less chance of wrong results.
5. To bring the ancient RAID logic to fit the rest of inxi style, made
zfs, mdraid, and lvm raid components use incrementing numbers, like cpu
cores does. This got rid of the kind of ugly hacks used previously
which were not the same for zfs or mdraid, but now they are all the same,
except that the numbers for mdraid are the actual device numbers that
mdraid supplies, and the LVM and ZFS numbers are just autoincremented,
starting at 1.
6. Changed message <root/superuser required> to <superuser required> because
it's shorter and communicates the same thing.
INTERNAL CODE CHANGES:
1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All
tests passed, no legacy code issues in inxi as of now.
2. Although most users won't notice, a big chunk of inxi was refactored
internally, which is why the new -L, the revamped -R, and the fixed
disk totals finally all can work now. This may hopefully result in more
consistent output and fewer oddities and randomnesses, since more of the
methods all use the same tools now under the covers. Ths refactor also
significantly improved inxi's execution speed, by about 4-5%, but most
of those gains are not visible due to the added new features, but the
end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but
does more, and does it better, internally at least. If you have a very
good eye you may also note a few places where this manifests externally
as well. Last I checked about 10-12% of the lines of inxi had been changed,
but I think that number is higher now. Everything that could be optimized
was, everything could be made more efficient was.
3. Several core tools in inxi were expanded to work much more cleanly,
like reader(), which now supports returning just the index value you want,
that always happened on the caller end before, which led to extra code.
get_size likewise was expanded to do a string return, which let me
remove a lot of internal redundant code in creating the size unit output,
like 32 MiB. uniq() was also redone to work exclusively by reference.
4. Many bad reference and dereference practices that had slipped into inxi
from the start are mostly corrected now, array assignments use push now,
rather than assign to array, then add array to another array, and assign
those to the master array. Several unnecessary and cpu/ram intensive copying
steps, that is, were removed in many locations internally in inxi. Also
now inxi uses more direct anonymous array and hash refernce assignments,
which again removes redundant array/hash creation, copy, and assignment.
5. Also added explicit -> dereferencing arrows to make the code more clear
and readable, and to make it easier for perl to know what is happening.
The lack of consistency actually created confusion, I was not aware of
what certain code was doing, and didn't realize it was doing the same
thing as other code because of using different methods and syntaxes for
referencing array/hash components. I probably missed some, but I got many
of them, most probably.
6. Instituted a new perl builtin sub routine rule which is: if the sub
takes 2 or more arguments, always put in parentheses, it makes the
code much easier to follow because you see the closing ), like:
push(@rows,@row); Most perl builtins that take only one arg do not
use parentheses, except length, which just looks weird when used in
math tests, that is: length($var) > 13 looks better than length $var > 13.
This resolved inconsistent uses that had grown over time, so now all the
main builtins follow these rules consistently internally.
Due to certain style elements, and the time required to carefully go through
all these rules, grep and map do not yet consistently use these rules, that's
because the tendency has been to use the grep {..test..} @array and
map {...actions...} @array
7. Mainly to deal with android failures to read standard system files due to
google locking it down, moved most file queries to use -r, is readable, rather
than -e, exists, or -f, is file, unless it only needs to know if it exists,
of course. This fixed many null data errors in android even on locked androids.
8. Added in %mapper and %dmmapper hashes to allow for easy mapping and
unmapping of mapped block devices. Got rid of other ways of doing that,
and made it consistent throughout inxi. These are globals that load once.
9. Learned that perl builtin split() has a very strange and in my view originally
terrible decision that involves treating as regex rules string characters in split
string, like split('^^',$string), which should logically be a string value, not
a ^ start search followed by a ^, but that's how it is, so that was carefully checked
and made consistent as well. Also expanded split to take advantage of the number of
splits to do, which I had only used occasionally before, but only updated field/value
splits where I have a good idea of what the data is. This is very useful when the
data is in the form of field: value, but value can contain : as well. You have to
be very careful however, since some data we do want in fact the 2nd split, but not
the subsequent ones, so I only updated the ones I was very sure about.
10. Going along with the cpu microarch fixes, updated and cleaned up all the lists
of model/stepping matches, now they are all in order and much easier to scan and
find, that had gotten sloppy over the years.
11. More ARM, moved dummy and codec device values into their own storage arrays,
that let me remove the filters against those in the other detections. Makes logic
easier to read and maintain as well.
2020-12-15 23:13:14 +00:00
|
|
|
Only use the following in conjunction with \fB\-\-debug 2[012]\fR, and only
|
2018-09-28 21:54:00 +00:00
|
|
|
use if you experienced a failure or hang, or were instructed to do so.
|
|
|
|
|
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
.TP
|
New version, new man.
Bugs:
1. If you consider failure to identify a mounted yet hidden partition a bug, then
that bug is fixed, but I consider that as more of a fix than a bug.
Fixes:
1. Added more device pattern ID for odroid C1 and C2, these are now pretty well
supported.
2. inxi failed to handle a certain type of hidden partition, so far only seen
with udiskctl mounted TimeShift partitions, but this may be a more general udisk
issue, but so far not enough information. The fix is to use the lsblk data to
build up missing partitions, so this fix is for non legacy Linux systems only.
The fix works pretty well, but it's hard to know until we get a lot more real
world data, but given so far I've received only one issue report on it, I
suspect this is not a common situation, but you never know, it would never
have shown up in datasets unless I had looked specifically for it, so it may
be more common than I think.
3. Cleaned up and simplified new --admin -p and -d logic.
Enhancements:
1. For debugging, renamed all user debugger switches to have prefix --debug.
These options are to help debug debugger failures, and so far have been tested
and solved the failures, so I'm adding them all to the main man and help menu,
thus raising them to the level of supported tools. These were enormously helpful
in solving proc or sys debugger hangs.
* --debug-proc
* --debug-proc-print
* --debug-no-sys
* --debug-sys
* --debug-sys-print
2. Added findmnt output to debugger, that may be useful in the future. Also added
df -kTPa to also catch hidden partitions in debugger.
3. Added in another user level debugger, triggered with --debug-test-1 flag. This
will do whatever operation is needed at the time for that user. Some issues can
only be resolved by the user on their machine.
4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!
2018-09-28 21:25:17 +00:00
|
|
|
.B \-\-debug\-proc\fR
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Force debugger to parse \fB/proc\fR directory data when run as root. Normally
|
|
|
|
|
this is disabled due to unpredictable data in /proc tree.
|
New version, man page. New features and fixes!
Bugs:
1. -I line, sometimes running in showed sudo. This is hopefully now corrected.
Fixes:
1. CPU architectures, small reordering based on hopefully more reliable data
source, but these are hard to find conclusively.
2. -S Distro id: switched ordering of prefered os-release sources, PRETTY_NAME
is not being used consistently, too many distros leave out the distro id found
in VERSION, so now it uses NAME + VERSION if both are there, then PRETTY_NAME
as a fallback. That reverses how it was, but it will provide better results for
most distros. Distros that did this properly to begin with should see no change.
3. Now that inxi is basically debugged and working, I've removed the output of
'inxi' from the -t lines. It remains for the pinxi branch however so you can
see how many resources pinxi uses to run.
4. ipmi sensors data are proving to be as random as lm-sensors. Added another
alternate syntax for sensors.
5. CPU: found an alternate syntax, again, for IPMI and sensors data, added
support, I hope, for that.
Enhancements:
1. Added /proc debugger tool to debugger. Due to oddities with how the /proc file
system is created, it will only run as user, not root, unless the --proc flag is
used. More programs added to debugger commands.
2. More disk vendor strings added, fine tuning of vendor detections. There is a
tendency in NVMe disk names to put the vendor name in the middle of the string.
That is now handled for a few key vendors.
3. Added basic ARM SOC and server support. This will require more work in the future
because the syntax used varies significantly device to device, but the featuers
are now in place to add that support. Most SBC ARM devices should now at least show
the model and details data in machine data, and some will show -G -A -N data as
well.
4. ARM CPU: added first attempt to show the cpu variant as well as the more
generic ARM data. This shows 1 or more variants, some ARM devices have two different
cpu cores running at different speeds. Odroid for example.
5. Added system 'base:' data for -Sx, that modifies Distro: in supported cases.
Currently only Mint and MX/AntiX supported because each specific distro must be
handled explicitly using empirical file based data tests. I decided against showing
this for rolling release, since really everyone knows that Antergos is made from
Arch Linux, so showing that does not provide much useful information, whereas
showing the Ubuntu version Mint was made from does.
Note that several derived distros are changing how they use os-release, so the
tools had to be revised to be more dynamic, which is a pain, and makes it even
more empirical and less predictable to print what should be trivially easy to
gather distro and derived source data.
If your distro is not in this list and you want the base data to be present, please
supply a --debug 22 dataset so I can check all the files required to make the
detection work. If your distro has changed methods, please note which methods
were used in the past, and which are used now.
6. Added Armbian distro detection, that's tricky. Added Rasbpian detections.
Added improved Antergos, Arco, and maybe Chakra, Arch detections.
7. Big one: Hardware RAID basic support added. Note that each vendor, and
unfortunatley, often each product line, has its own raid status and drive
reporting tools, which makes adding the actual drive/raid/status report part
very time consuming to add. I may only support this if a certain software maker's
raid tools are installed because they are much simpler to parse, but for now,
it only shows the presence of the raid device itself, not disks, raid status, etc.
2018-06-23 18:32:18 +00:00
|
|
|
|
New version, new man.
Bugs:
1. If you consider failure to identify a mounted yet hidden partition a bug, then
that bug is fixed, but I consider that as more of a fix than a bug.
Fixes:
1. Added more device pattern ID for odroid C1 and C2, these are now pretty well
supported.
2. inxi failed to handle a certain type of hidden partition, so far only seen
with udiskctl mounted TimeShift partitions, but this may be a more general udisk
issue, but so far not enough information. The fix is to use the lsblk data to
build up missing partitions, so this fix is for non legacy Linux systems only.
The fix works pretty well, but it's hard to know until we get a lot more real
world data, but given so far I've received only one issue report on it, I
suspect this is not a common situation, but you never know, it would never
have shown up in datasets unless I had looked specifically for it, so it may
be more common than I think.
3. Cleaned up and simplified new --admin -p and -d logic.
Enhancements:
1. For debugging, renamed all user debugger switches to have prefix --debug.
These options are to help debug debugger failures, and so far have been tested
and solved the failures, so I'm adding them all to the main man and help menu,
thus raising them to the level of supported tools. These were enormously helpful
in solving proc or sys debugger hangs.
* --debug-proc
* --debug-proc-print
* --debug-no-sys
* --debug-sys
* --debug-sys-print
2. Added findmnt output to debugger, that may be useful in the future. Also added
df -kTPa to also catch hidden partitions in debugger.
3. Added in another user level debugger, triggered with --debug-test-1 flag. This
will do whatever operation is needed at the time for that user. Some issues can
only be resolved by the user on their machine.
4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!
2018-09-28 21:25:17 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-proc\-print\fR
|
|
|
|
|
Use this to locate file that /proc debugger hangs on.
|
|
|
|
|
|
New version, new man. Fixes, stitches, and returns!!
Bugs:
1. As a fix (3), failure to handle spaces in mount source names. More of a fix than
a bug, since it was an old issue #63.
2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data
tripping null data or unreadable file errors, but I'll call those bugs since they
look like bugs to end users. See Fixes for more.
3. See Fix 4, this is sort of a bug, inxi failed to return expected values on
success/failure.
Fixes:
1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented
internally. This is now corrected.
2. Apple OSX was returning errors, those were fixed.
3. Finally handled ancient issue #63, support now there for spaces in remote source
name. This means that both spaces in source block name, and mount point name, are
in theory both handled now. This was also to fix an osx issue #164 despite the
fact that technically I do not support osx beyond fixing errors, but since in this
case the issue was a long standing one, I fixed it for everything.
4. Big fix, I'd completely left undone proper unix type error number returns in
inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi
returns integer success/error numbers as expected.
5. OSX xml based version info broke, of course, naturally it would, so I added in
an osx fallback where if no distro version detected, use fallback unix method, which
is what all the other unices use.
6. Along with space in source name, fixed mapped handling a bit more too for
partitions.
6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure
how I'd missed those for so long.
7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a,
sigh, human readable default format, in M, so to handle this for all bsds, I had
to make a dynamic column detection for avm and fre, and use those after, and also
i had to add in a M detection, if found, *1024 and strip out M, sigh.
8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks
does not always use the same order in comma separated list, saw user case where
the first item after : was the MB size, not the second. Made detection dynamic.
9. Due to Android case, found types where no cpu speed data was found, no max speed
at least, which tripped an error due to null data for ARM, this is now handled,
now cpu speed min/max read permissions in /sys are checked first before trying to
read, and default failures are better handled.
10. On man page, added in clarification of the moving of Memory: item from Info:
line to ram Memory: line, explaining when it appears where. I do not removing the
item from -I, I may revert that change, I find it non-intuitive to move that
around.
Enhancements:
1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this
closes issues #166 #165 #162
2. Improved documentation a bit to avoid ambiguity re how to get colors in output.
That handles issue #161, thanks fugo for the nudge to improve the documentation.
3. First inxi on Android tests, using termux, which has a debian based apt
type installer, got inxi running on at least two devices, including pixel2, but
discovered that apparently as of android 5, /sys is now locked up in terms of
wildcard reads, but further analysis is required, but as of now, inxi works in
termux, but fails to get any Device data for A, G, or N. Thus it also fails to match
IF to Device, so none of the IP data shows up. The latter will probably be fixed
since Android has ip and ifconfig already, or termux does, but so far I found no
way to get device data for ARM in Android 5.x and greater (checked on
android 7 and 9 in real phones).
4. More disk vendors!! thanks linuxlite / linux hardware database for offering an
apparently never ending list of obscure and not so obscure disk vendors and
products.
5. While I was unable to get confirmation or documentation on file names for
tce repo files, I guessed that localmirrors would be used, but this may be
any random text file in /opt at all, no extensions, I'd have to test to confirm
or deny possible values.
6. To handle more complex debugger failures, added --debug-no-proc,
--debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.
Changes:
1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful
and reliable than I'd first expected when I made the feature, the -xxx was more
an indication of my lack of trust in the method and source, but so far it seems
pretty good, so I bumped it up to an -x option. Note that also, it's quite useful
to know the vendor of, say, your network or graphics card, not just the actual
device internal data, which is all inxi has ever shown previously.
2. Small change, if no partition type data is found, dev, remote, mapped, default
now says 'source:' instead of 'dev:' which makes more sense. Note that df calls
that column 'source', so I decided to go with their language for the default not
found case. Also changed mapped to say mapped. This was part of a bit of a
refactor of the partition type logic, enhanced by adding mapped to existing types,
and moved the entire type detection block into the main data generator, and out
of the data line constructor.
Optimizations:
1. Tested, and dumped, List::Util first() as a possible way to speed up grep
searches of arrays, where the goal is just to see if something is in an array. My
expectation was that first(), returning the first found instance of the search term,
would of course be faster since it will always exit the search loop was met with
the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin.
I tested this fairly carefully, and used NYTProf optimizer tool and the results were
totally consistent, first() was always much slower than grep(), no matter what size
the array is. I assume this means the core C programming that makes grep is simply
much better than the File::Util module programming that makes first(). Removed
first() and now know that nothing will be faster than grep so no need to look there
for speed improvements.
The moral of the story: just because something should in theory be faster, does
sadly not mean it will be faster, for there are bigger things at work, skill of
the programmers who made the logic, how perl handles external vs internal tools,
and so on. As an aside, this forms a fairly consistent pattern where I've found
Perl by itself to be faster than modules in many cases, that is, it's faster to
write the code out than to use a module in many cases that I have tested, so I
will always test such ideas and dump every one that is in fact slower than native
Perl builtins.
2018-10-14 23:16:06 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-no\-exit\fR
|
|
|
|
|
Skip exit on error when running debugger.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-no\-proc\fR
|
|
|
|
|
Skip /proc debugging in case of a hang.
|
|
|
|
|
|
New version, new man.
Bugs:
1. If you consider failure to identify a mounted yet hidden partition a bug, then
that bug is fixed, but I consider that as more of a fix than a bug.
Fixes:
1. Added more device pattern ID for odroid C1 and C2, these are now pretty well
supported.
2. inxi failed to handle a certain type of hidden partition, so far only seen
with udiskctl mounted TimeShift partitions, but this may be a more general udisk
issue, but so far not enough information. The fix is to use the lsblk data to
build up missing partitions, so this fix is for non legacy Linux systems only.
The fix works pretty well, but it's hard to know until we get a lot more real
world data, but given so far I've received only one issue report on it, I
suspect this is not a common situation, but you never know, it would never
have shown up in datasets unless I had looked specifically for it, so it may
be more common than I think.
3. Cleaned up and simplified new --admin -p and -d logic.
Enhancements:
1. For debugging, renamed all user debugger switches to have prefix --debug.
These options are to help debug debugger failures, and so far have been tested
and solved the failures, so I'm adding them all to the main man and help menu,
thus raising them to the level of supported tools. These were enormously helpful
in solving proc or sys debugger hangs.
* --debug-proc
* --debug-proc-print
* --debug-no-sys
* --debug-sys
* --debug-sys-print
2. Added findmnt output to debugger, that may be useful in the future. Also added
df -kTPa to also catch hidden partitions in debugger.
3. Added in another user level debugger, triggered with --debug-test-1 flag. This
will do whatever operation is needed at the time for that user. Some issues can
only be resolved by the user on their machine.
4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!
2018-09-28 21:25:17 +00:00
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-no\-sys\fR
|
|
|
|
|
Skip /sys debugging in case of a hang.
|
|
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-sys\fR
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
Force PowerPC debugger parsing of /sys as doas/sudo/root.
|
New version, new man.
Bugs:
1. If you consider failure to identify a mounted yet hidden partition a bug, then
that bug is fixed, but I consider that as more of a fix than a bug.
Fixes:
1. Added more device pattern ID for odroid C1 and C2, these are now pretty well
supported.
2. inxi failed to handle a certain type of hidden partition, so far only seen
with udiskctl mounted TimeShift partitions, but this may be a more general udisk
issue, but so far not enough information. The fix is to use the lsblk data to
build up missing partitions, so this fix is for non legacy Linux systems only.
The fix works pretty well, but it's hard to know until we get a lot more real
world data, but given so far I've received only one issue report on it, I
suspect this is not a common situation, but you never know, it would never
have shown up in datasets unless I had looked specifically for it, so it may
be more common than I think.
3. Cleaned up and simplified new --admin -p and -d logic.
Enhancements:
1. For debugging, renamed all user debugger switches to have prefix --debug.
These options are to help debug debugger failures, and so far have been tested
and solved the failures, so I'm adding them all to the main man and help menu,
thus raising them to the level of supported tools. These were enormously helpful
in solving proc or sys debugger hangs.
* --debug-proc
* --debug-proc-print
* --debug-no-sys
* --debug-sys
* --debug-sys-print
2. Added findmnt output to debugger, that may be useful in the future. Also added
df -kTPa to also catch hidden partitions in debugger.
3. Added in another user level debugger, triggered with --debug-test-1 flag. This
will do whatever operation is needed at the time for that user. Some issues can
only be resolved by the user on their machine.
4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!
2018-09-28 21:25:17 +00:00
|
|
|
|
|
|
|
|
.TP
|
|
|
|
|
.B \-\-debug\-sys\-print\fR
|
|
|
|
|
Use this to locate file that /sys debugger hangs on.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.SH SUPPORTED IRC CLIENTS
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
BitchX, Gaim/Pidgin, ircII, Irssi, Konversation, Kopete, KSirc, KVIrc,
|
|
|
|
|
Weechat, and Xchat. Plus any others that are capable of displaying either
|
|
|
|
|
built\-in or external script output.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH RUNNING IN IRC CLIENT
|
2018-04-06 22:52:08 +00:00
|
|
|
To trigger inxi output in your IRC client, pick the appropriate method from the
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
list below:
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
2018-07-23 20:40:49 +00:00
|
|
|
.B Hexchat, XChat, Irssi
|
2016-10-29 22:15:43 +00:00
|
|
|
\fR(and many other IRC clients)
|
2018-04-04 06:41:06 +00:00
|
|
|
.B /exec \-o inxi \fR[\fBoptions\fR]
|
2018-04-06 22:52:08 +00:00
|
|
|
If you don't include the \fB\-o\fR, only you will see the output on your local
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
IRC client.
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
|
|
|
|
.B Konversation
|
2018-04-06 22:52:08 +00:00
|
|
|
.B /cmd inxi
|
2016-10-29 22:15:43 +00:00
|
|
|
\fR[\fBoptions\fR]
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
To run inxi in Konversation as a native script if your distribution or inxi
|
|
|
|
|
package hasn't already done this for you, create this symbolic link:
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
KDE 4:
|
2017-06-09 17:14:28 +00:00
|
|
|
.B ln \-s /usr/local/bin/inxi /usr/share/kde4/apps/konversation/scripts/inxi
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
KDE 5:
|
2017-09-22 00:12:58 +00:00
|
|
|
.B ln \-s /usr/local/bin/inxi /usr/share/konversation/scripts/inxi
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
If inxi is somewhere else, change the path \fB/usr/local/bin\fR to wherever it
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
is located.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
If you are using KDE/QT 5, then you may also need to add the following to get
|
2018-04-04 06:41:06 +00:00
|
|
|
the Konversation \fR/inxi\fR command to work:
|
2017-09-22 00:12:58 +00:00
|
|
|
|
|
|
|
|
.B ln \-s /usr/share/konversation /usr/share/apps/
|
|
|
|
|
|
This release fixes another very long standing bug, which I was not sure was an
inxi or a Konversation bug, which made tracking it down very difficult. Special
thanks to argonel of Konversation for helping solve this problem, or at least,
for directing my attention towards the likely cause area, and away from wrong
ideas. The bug was that inxi simply did not run in Konversation, it would exit
with error when run with /cmd or /inxi via symbolic links.
This may not seem like a huge deal to many of you, but the actual history of
inxi was directly linked to user support in mainly Konversation, so this feature
not working I have alwyas found extremely annoying, but I could never figure out
why it wasn't workiing, and didn't really know where to start until Argonel
helped narrow it down to a specific Konversation function in inxi. At which
point tracking down the real bug was fairly easy. Since testing in IRC is always
a key test point for inxi features and releases, not working in my main GUI IRC
client forced me to use CLI clients like irssi, via /exec -o inxi.
There was a secondary cause of failure, which was missing a key qdbus package,
which made figuring this one out a two step process.
So inxi is once again working in all areas, with no known significant failure
areas beyond known issues that have no current solution, or which I don't feel
like doing.
But possibly more important, a goal I have had for a while now of doing long
needed code refactors, bug fixes, without huge new code blocks or features
adding new future fixes and bugs, has been slowly happening.
This was quite important, because inxi's codebase and logic is so complex and
large now that at some point, it required rest and cleanup and corrections,
without continuously adding new code and logic, which would then trigger new
fixes and bugs. In other words, the code is taking a long needed, and well
deserved, breather, to recover after huge increases in the overall LOC and
feature sets.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. No known way to detect that the system might be Wayland for the Graphics:..
API: fixes, unless Xwayland is installed if the wayland protocol detections
failed, which they often do in console. Not practical to look for all compositor
variants on system to determine if it could be Wayland if not X or Xvesa, so
that one will just be what it is, which is fine, definitely better than it was
before. Note this is only an issue if in Console, no Display. Note that if inxi
is run as root, Wayland data also usually fails, even in Display.
--------------------------------------------------------------------------------
BUGS:
1. Another corner case monitor position issue, applied fallback primary monitor
rule when a primary monitor had already been located. This is corrected via a
graphics global $b_primary which once set will disable this fallback feature.
Objectively, the fallback feature should just be removed. The test is if that
monitor is not primary, and if position is 0x0, then assume primary, without
verifying no primary had been located yet.
2. A super old bug, in current konversation, was failing to trip the konvi
detections, which then resulted in not stripping off the first two args in
@ARGV, which then resulted in bad args being passed to inxi on konvi start,
which then resulted in silent failing. Many thanks to argonel of #konversation
for the patience to help me figure out what was going on with this bug. He's
been a Konversation developer probably longer than I've been doing inxi.
Cause was very tricky and subtle, the ps aux path for konvi had changed
slightly, not the path, but the pattern, it used to be:
konversation -session [sessin id]
but it's changed to:
konversation -qwindowtitle Konversation
or just plain:
konversation as line ending.
This led to failure to find konvi running, which then made the konvi ids fail.
Also, this would not work if the qdbus-qt5 package was not installed, or other
distros might have that packaged differently. Because of these dual causes, I
was simply unable to figure out what was going on for many years. I suspect this
stopped working with KDE 5/QT 5, but I'm not sure.
3. Used wrong key names for some ZFS tests and fallbacks, those could have led
to failures though very difficult to test and verify this. Also see fix 5, which
of course also looks like a bug, acts like one, but was actually due to a new
use of /dev/disk/by-partuuid for ZFS components in Ubuntu which inxi had not
seen before.
--------------------------------------------------------------------------------
FIXES:
1. Alternate ps IDs for appimage detection (try appimagelauncher), alternate
paths for possible appimage storage locations (also try ~/.appimage/*). File
names might be *.appimage or *.AppImage, probably other variants too.
2. Going along with Change 1, made tests more granular for missing graphics API
type data. Also updated messages to be more correct and clear, in and out of
display. This corrects an issue I'd seen but never resolved, which was on
headless systems showing this message:
Message: GL data unavailable in console. Try -G --display
Now the tests are far more granular, and only show that if glxinfo is installed,
and also shows specific messages if glxinfo not installed, but X/Xorg present,
or, for Wayland, if Xwayland present. These all get their own specific messages
now, and generally will also show which API is being used, or API: N/A if
nothing is detected, as in the case of a headless system with no X, Wayland,
etc.
3. Github issue #275 on of all things Microsoft WSL environment, has a small
glitch with undefined display hz, but otherwise inxi seems to work in that
environment, albeit missing many data types!
4. Made tests for konversation more robust, including test for
$ENV{'PYTHONPATH'} containing konversation in path, which I believe will work
for all new Konversations (KDE 5 and newer), and be much faster. The previous
tests are now more robust and less prone to failure, and only activate when
PYTHONPATH is not present with konversation string present as well.
5. Fix for ZFS using /dev/disk/by-partuuid for partition id in zfs,
which can lead to wrong usable disk total size report, along with failure
to show components. Thanks delanym, issue #276 for reporting this problem, which
also exposed some harder to trigger bugs in ZFS (Bug 3).
6. Exposed by issue #276, case where line was wrapping value when value was too
short visually to value: used: 34.4 GiB (4.5%) due to the 3 or more words
trigger to enable wrapping of value, but noticed that if length of line was
exactly max-width, not > or <, it might vanish.
7. Case where no X or GPU drivers found, but dri driver detected, was not
showing, now does.
8. OpenRC is the init system in some cases, that is: readlink /sbin/init >
/sbin/openrc-init, where /proc/1/comm == init. Was showing only as OpenRC rc
type, which wasn't actually correct.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. New nvidia gpu product ids for Turing, Ampere, Lovelace, Hopper. New Intel
GPU ids.
2. Added Zinc to systembase/distro, needs slightly special handling to get both
names right. Also added Tuxedo, which could use existing methods.
3. Added dpkg tool nala, which is sort of a CLI front end for apt, zinc uses it,
but it's also in Debian main package pool. Also deb-get, which is another zinc
thing for package management.
4. Full support for dinit: version, dinitctl w/status in ServiceData
4. Added initial support for init systems: 31init (31 line C program, no
--version), Hummingbird (unknown if -v/--version).
5. A few new CPU arch ids (new Intels).
--------------------------------------------------------------------------------
CHANGES:
1. Going somewhat along with the change in Audio to call ALSA a Sound API
instead of a sound server, changed key name OpenGL: to API: OpenGL in Graphics.
Also for EGL wayland, calling that the api too.
https://en.wikipedia.org/wiki/OpenGL
This conforms more closely to how these things are defined. Note that once
again, a value had been used as a key name, which almost always indicates a
failure to understand something about the core tech.
2. Changed wrapping of values from 3 words or more to 3 or more words AND length
> 24 characters. Saw example of:
.... used: 28.45 GiB
(4.5%)
which isn't desirable.
3. Changed minimum wrap to 60 columns, the new wrapper features are working so
well that if users want output that short, it will usually work fine, except of
course for very long word strings like a kernel name or parameter.
Note that this does not truncate long 'words' that might be wrapped, or going
along with Change 2, long 'sentences' of 2 words, those will always appear on
the same line regardless. For 'sentences' of 3 or more words, however, it goes
word by word, so it could well wrap after the first word, and so on. Obviously,
a 24 or fewer character value will never be wrapped, which was the intended
correction of change 2.
4. Going with Fix 8, OpenRc is an init system when it owns /proc/1/comm, had not
realized that /proc/1/comm == init can map to dinit, openrc as init. Now will
only show OpenRc as rc: type if not init as well.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updates in man for Change 1.
2. Added to docs/inxi-graphics.txt good quote re EGL/GBM, as well as VBE/GOP for
vesa. Trying to find docs where they actually say clearly it's an API is
remarkably difficult.
3. Man page, added note about Konversation requiring qdbus-qt5 (Debian+),
qt5-qttool (RHEL+/SUSE+), qt-tools (Arch+) for inxi to work inside it. Also
updated smxi.org/docs/inxi-usage.txt to note requirements for Konversation use
and setup.
4. Man, help, changed min width for -y/--width from 80 to 60.
5. docs/inxi-values.txt updated for --cygwin, --wsl fake OS type switches. Not
technically the OS, more the environment, but close enough.
6. docs/inxi-init.txt updated for new init types.
--------------------------------------------------------------------------------
CODE:
1. Refactored tools/gpu_ids.pl to correct and enhance some features.
2. Renamed functions and sections to better reflect that the display interface
is an API, this makes stuff less odd internally, and makes the function/variable
names correspond better to what the stuff really is.
3. Commented out kde konversation data source config collector, that logic looks
like it never worked, and couldn't work, since it never actually located
inxi.conf files, just paths to the data directories.
4. Expanded release.pl to handle acxi docs as well, makes it all consistent and
a lot easier to do long term.
5. Fake --wsl WSL switch, not really used, but in case.
6. Changed $b_cygwin to $windows{'cygwin'} and added $windows{'wsl'}.
7. Added -WSL to debugger string generator once WSL type is detected.
8. Refactored init, runlevel functions get_init_data() (now InitData::get()),
get_runlevel_data() (now InitData::get_runlevel()), get_runlevel_default() (now
InitData::get_runlevel_default()) into one package/class: InitData. This should
have been done a long time ago, to follow the general rule "if > 1 functions for
a tool refactor it into a class/package" for when to create a package/class
internally.
9. Completed gpu_ids.pl, now outputs the full hash set per item, so entire
blocks can be copied/pasted over. Something of a pain to get comments included,
which aren't strictly necessary in pinxi itself, but they do help read the
hashes for gpu data.
2022-10-31 22:47:31 +00:00
|
|
|
Make sure you also have the \fRqdbus\-qt5\fR package (Debian/Ubuntu + derived),
|
|
|
|
|
\fRqt5\-qttools\fR (Fedora/RHEL/SUSE + derived), \fRqt5\-tools\fR (Arch +
|
|
|
|
|
derived) installed (for KDE 5/QT 5, check distros for future package names),
|
|
|
|
|
\fRqt5\-tools\fR (Arch + derived). Check your distro if the program is missing.
|
|
|
|
|
Depending on the distro, \fR/usr/lib/qt5/bin/qdbus\fR is required, which in
|
|
|
|
|
Debian+ is provided by the above package.
|
|
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
Then you can start inxi directly, like this:
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.B /inxi
|
2016-10-29 22:15:43 +00:00
|
|
|
\fR[\fBoptions\fR]
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
|
|
|
|
.B WeeChat
|
2018-04-06 22:52:08 +00:00
|
|
|
.B NEW: /exec \-o inxi
|
2016-10-29 22:15:43 +00:00
|
|
|
\fR[\fBoptions\fR]
|
2014-04-03 18:35:14 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.B OLD: /shell \-o inxi
|
2016-10-29 22:15:43 +00:00
|
|
|
\fR[\fBoptions\fR]
|
2014-04-03 18:35:14 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
Newer (2014 and later) WeeChats work pretty much the same now as other console
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
IRC clients, with \fB/exec \-o inxi \fR[\fBoptions\fR]. Newer WeeChats
|
|
|
|
|
have dropped the \fB\-curses\fR part of their program name, i.e.:
|
New version, new tarball, new man page. This is the first attempt to correct an
issue a forum poster raised, which is the fact that despite the fact that GNU/Linux
has had reasonably ok zfs support for years now, inxi only tested for zfs on bsd
systems.
This has been corrected. Due to the complexity of handling software raid, inxi
will now test first for ZFS data, if none is found, it will then test for
/proc/mdstat.
In a perfect world I'd like to have full dynamic Raid support, but I'm missing
all the key ingredients required to add that:
1. systems to test on
2. software raid, I don't use it
3. data collection for non mdraid and zfs software raid, including the values
possible to gather from all non software raid.
Basically, the only way I'd extend -R raid option is if I get direct ssh access to
a machine that uses the alternate software raid type, otherwise it would take
forever to figure out the options.
Since the number of people who might be actually running zfs and mdraid and
using inxi probably numbers in the 10 globally, I figured this solution was a fine
way to handle adding zfs without messing up mdraid, which is more common on linux.
It also does not break BSDs, since bsds as far as I know don't use mdraid, and don't
have /proc/mdraid in the first place.
Also redid the man page to add -! 41, -! 42, -! 43, -! 44 options, which bypass
curl, fetch, wget, and all of them, respectively. Plus making the lines less wide.
That should make those people who actually use 80 column wide vi as an editor
happy, lol.
2017-11-29 01:23:41 +00:00
|
|
|
\fBweechat\fR instead of \fBweechat\-curses\fR.
|
2014-04-03 18:15:23 +00:00
|
|
|
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
.SH CONFIGURATION FILE
|
2018-04-06 22:52:08 +00:00
|
|
|
inxi will read its configuration/initialization files in the
|
|
|
|
|
following order:
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fB/etc/inxi.conf\fR contains the default configurations. These can be
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
overridden by creating a \fB/etc/inxi.d/inxi.conf\fR file (global override),
|
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
Some very nice issue reports have helped correct various corner case issues.
Mint users helped find a big one with lspci.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Unsure how to handle Android case where inxi correctly does -r test, see bug
3 fixes 6, but android incorrectly claims it is readable when it is not
readable, then the reader tool can't read the file and fails with permissions
error. This is one of those weird android errors that are pretty much impossible
to fully work around, but we can get rid of the readline() errors when reader()
was trying to work on a file handle that did not exist, that part was an inxi
bug.
--------------------------------------------------------------------------------
BUGS:
1. dm detection was not using case sensitive search for duplicates, leading to
cases where dm like slim / SLiM failed to get detected and then repeated in
output. Anonymous BSD debugger dataset exposed this issue, thanks.
2. In certain corner cases, like ARM Android, sub reader got passed a file that
had passed the is readable -r test, but it still failed with permissions error,
which then led reader to try to keep working with a null $fh. While in theory
nothing non readable should be passed to reader(), that fails when the OS fails
to actually follow correct readable rules, as in this case. Added protections in
reader() to handle this case, now will show error, but will not try to work with
$fh, that is how it should have been all along, but this is a very corner case.
Exposed by an anoymous ARM debugger dataset.
Thanks Termux user for creating the debugger dataset that exposed this issue.
3. lspci parser didn't null port value each iteration, resulting in all pci
items getting port values. Not a big deal, port is only used one place, but good
to find and correct that error.
4. Not an inxi bug, but would appear so to end users: lspsci -nnv implements a
truncating routine and breaks the first line for each bus id. See Fix 6 and Code
fix 3.
--------------------------------------------------------------------------------
FIXES:
1. -S and -I would show Console: tty pts/3 even though pts device is a pty, not
a tty. The only time this happened was when connecting to a remote system using
ssh or something like that. Local console still shows Console: tty 2 since that
was correct, but Console: tty pts/2 was confusing since technically it's not a
tty, it's a pty, pseudo terminal.
Now shows, when relevant: Console: tty 2 OR Console: pty pts/2.
2. Issue #252 notes that Emacs (and possibly other code/text editors with native
embedded terminals) includes a native virtual terminal that also follows
configuration rules from the editor to highlight trailing spaces. This created
odd looking screen output in Emacs vt mode since inxi always sets key/value
pairs with a white space ending as separator for next key value pair for screen
output mode, resulting always in a trailing space on each vt screen line. Fix
was to remove the last trailing space just prior to the print line point to
avoid this issue.
As a general thing, I'm curious to learn if any editor other than Emacs actually
contains its own virtual terminal that also follows the editor rules for output.
Or if any virtual terminal has such a highlight trailing space rule, which would
be imo so annoying it's hard to understand why a vt would implement it. Easy to
understand why Emacs (or any editor) does it, but an editor also being a vt AND
applying certain editor display configurations to the vt is a very specific and
unique circumstance I'd say.
Odd, historical, but there it is, why not handle it?
3. ARM / Android case where certain files passed the read -r test, but failed
with permission denied error. This tripped a further glitch where reader() would
then try to work with the failed $fh, see bug 2. This was really more a fix
than a bug, since the bug in this case was in android permissions tests, not
inxi, but it appears to be a bug to end users, so it's handled now.
4. Another ARM/Android, there was a voltage regulator IP that contained the term
wlan so it tripped false positive for network match. Added a new type,
regulator, to filter out those, like codec and dummy do already.
5. For issue #254, fix for cygwin ERR-102 in partitions, add cygwin test, new
dev type, 'windows', dev base then becomes E: or whatever. To avoid confusing D:
for a key: with no value, added D:/ slash.
6. Mint people discovered lspci issue, lspci -nnv has a bug where it will
truncate the output of the first line per bus ID if it's over some arbitrary
amount, then tack on rev and other items to end of that string, which leads to
the block: [vendorID:productID] getting truncated or removed altogether. Clearly
an oversight, at least I hope it's an oversight on lspci's part, but have to
work around the issue anyway since it may never get fixed, and has been around a
long time. Bug is in lspci 3.7, 3.6.4, and probably earlier.
Also added in a fillin tool for this rare case, lspci -n data is used to replace
the missing values.
Note that while lspci recommends using -mmv, for machine parsing, apparently
nobody noticed that -mmv doesn't have the same data items as -nnv, sigh.
7. Issue #255 noted that the combination of:
GoogleDrive Hogne: fuse.rclone 15728640
which is two word remote fs AND a fs type with a '.' in it would fail to trip
the handler for that multi word remote mount name. Also failed to detect as
remote fs, added fs specific test since the actual mount name doesn't permit
reliable detection as remote type. Testing for trailing ':' isn't safe since
':' alone is not an invalid character in a file system name as far as I know.
Further, this exposed that the ^^ space replacements for $row[0] fs > 1 word
name were not being reset soon enough in the logic, that's also corrected.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Neglected to support standard package config file override
/etc/inxi.d/inxi.conf item. This is mainly useful for packaged inxi's who want
to override the distro maintainer /etc/inxi.conf file. Test priority is the same
except /etc/inxi.d/inxi.conf comes right after /etc/inxi.conf now in the test
sequence.
2. Added basic cygwin id, yes, inxi works in cygwin, apparently, with some
issues. Added cygwin os id to distro ids.
3. Added --version info for debugger, sometimes we want to know what verion of
a tool, like lspci, in case it has a bug or something.
4. Added exfat and apfs to unmounted fs types.
5. More disk vendors!! New vendor ID matches!! Yes, yes, you've heard it all
before, the list never ends!! The eternal chaos of existence manifested in just
how many IDs can be generated for new and old disk vendors alike!!!
--------------------------------------------------------------------------------
CHANGES:
1. No changes this release.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Pull request #253 corrected typos, urls, and other errors in man page,
inxi/pinxi comments, pinxi.1/inxi.1, README.txt, and updated LICENSE.txt to
current gnu wording.
--------------------------------------------------------------------------------
CODE:
1. Forgot to add lspci debugger fake data option, that's corrected. That's
--fake lspci, now works, didn't before, only the bsd pci tools had fake switches
previously, since lspci never needs debugging really, but did now to test an
issue report.
2. Added -CYGWIN to debugger file name. Added -ANDROID if ARM and if android.
3. With Fix 6, refactored entire lspci_data block, added lspci_n_data item,
which matches bus id of lspci -nnv when corruption occurs and replaces vendor,
product, and if also missing, rev version. I kind of knew I'd have to do this
fix one day, that was the same fix logic used on the BSD pci tools, which have
similar issues with consistency in output, or lack thereof.
This refactor is long term very good because it avoids an entire class of
possible errors, and makes pci detections far more robust.
4. Created new repo, for legacy code, inxi-legacy. Moved branch inxi-c to
inxi-legacy/xorg-c, moved branch xiin to /xiin, moved branch inxi-legacy (binxi)
to inxi-legacy/inxi-legacy. Those directories each contain all the files each
branch had in it.
This gets rid of some branches clutter, and nobody needs to see those anymore,
but if they care, they can look at them. Note that to do this, I had to merge
their histories, which was not that nice, but git is just really bad at this
type of stuff, so that's how it goes.
Times like this really make me miss svn's directory based branch approach...
5. Simplified sub fs_excludes, simplified regex constructors for all function
that use this data, made list more fault tolerate by adding global (fs)?(\d{0,2}
which means all file systems can have or not have 'fs' at end, and all can have
or not have a version number in string.
6. Exposed by issue #255, refactored slightly ordering of partition filter
logics and variable resets in the df output processing loop.
7. Added --fake partitions, to help debug odd corner cases like cygwin glitches.
2021-10-12 01:56:00 +00:00
|
|
|
which will prevent distro packages from changing or overwriting your edits. This
|
|
|
|
|
method is recommended if you are using a distro packaged inxi and want to
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
override some global configuration items from the package's default
|
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
Some very nice issue reports have helped correct various corner case issues.
Mint users helped find a big one with lspci.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Unsure how to handle Android case where inxi correctly does -r test, see bug
3 fixes 6, but android incorrectly claims it is readable when it is not
readable, then the reader tool can't read the file and fails with permissions
error. This is one of those weird android errors that are pretty much impossible
to fully work around, but we can get rid of the readline() errors when reader()
was trying to work on a file handle that did not exist, that part was an inxi
bug.
--------------------------------------------------------------------------------
BUGS:
1. dm detection was not using case sensitive search for duplicates, leading to
cases where dm like slim / SLiM failed to get detected and then repeated in
output. Anonymous BSD debugger dataset exposed this issue, thanks.
2. In certain corner cases, like ARM Android, sub reader got passed a file that
had passed the is readable -r test, but it still failed with permissions error,
which then led reader to try to keep working with a null $fh. While in theory
nothing non readable should be passed to reader(), that fails when the OS fails
to actually follow correct readable rules, as in this case. Added protections in
reader() to handle this case, now will show error, but will not try to work with
$fh, that is how it should have been all along, but this is a very corner case.
Exposed by an anoymous ARM debugger dataset.
Thanks Termux user for creating the debugger dataset that exposed this issue.
3. lspci parser didn't null port value each iteration, resulting in all pci
items getting port values. Not a big deal, port is only used one place, but good
to find and correct that error.
4. Not an inxi bug, but would appear so to end users: lspsci -nnv implements a
truncating routine and breaks the first line for each bus id. See Fix 6 and Code
fix 3.
--------------------------------------------------------------------------------
FIXES:
1. -S and -I would show Console: tty pts/3 even though pts device is a pty, not
a tty. The only time this happened was when connecting to a remote system using
ssh or something like that. Local console still shows Console: tty 2 since that
was correct, but Console: tty pts/2 was confusing since technically it's not a
tty, it's a pty, pseudo terminal.
Now shows, when relevant: Console: tty 2 OR Console: pty pts/2.
2. Issue #252 notes that Emacs (and possibly other code/text editors with native
embedded terminals) includes a native virtual terminal that also follows
configuration rules from the editor to highlight trailing spaces. This created
odd looking screen output in Emacs vt mode since inxi always sets key/value
pairs with a white space ending as separator for next key value pair for screen
output mode, resulting always in a trailing space on each vt screen line. Fix
was to remove the last trailing space just prior to the print line point to
avoid this issue.
As a general thing, I'm curious to learn if any editor other than Emacs actually
contains its own virtual terminal that also follows the editor rules for output.
Or if any virtual terminal has such a highlight trailing space rule, which would
be imo so annoying it's hard to understand why a vt would implement it. Easy to
understand why Emacs (or any editor) does it, but an editor also being a vt AND
applying certain editor display configurations to the vt is a very specific and
unique circumstance I'd say.
Odd, historical, but there it is, why not handle it?
3. ARM / Android case where certain files passed the read -r test, but failed
with permission denied error. This tripped a further glitch where reader() would
then try to work with the failed $fh, see bug 2. This was really more a fix
than a bug, since the bug in this case was in android permissions tests, not
inxi, but it appears to be a bug to end users, so it's handled now.
4. Another ARM/Android, there was a voltage regulator IP that contained the term
wlan so it tripped false positive for network match. Added a new type,
regulator, to filter out those, like codec and dummy do already.
5. For issue #254, fix for cygwin ERR-102 in partitions, add cygwin test, new
dev type, 'windows', dev base then becomes E: or whatever. To avoid confusing D:
for a key: with no value, added D:/ slash.
6. Mint people discovered lspci issue, lspci -nnv has a bug where it will
truncate the output of the first line per bus ID if it's over some arbitrary
amount, then tack on rev and other items to end of that string, which leads to
the block: [vendorID:productID] getting truncated or removed altogether. Clearly
an oversight, at least I hope it's an oversight on lspci's part, but have to
work around the issue anyway since it may never get fixed, and has been around a
long time. Bug is in lspci 3.7, 3.6.4, and probably earlier.
Also added in a fillin tool for this rare case, lspci -n data is used to replace
the missing values.
Note that while lspci recommends using -mmv, for machine parsing, apparently
nobody noticed that -mmv doesn't have the same data items as -nnv, sigh.
7. Issue #255 noted that the combination of:
GoogleDrive Hogne: fuse.rclone 15728640
which is two word remote fs AND a fs type with a '.' in it would fail to trip
the handler for that multi word remote mount name. Also failed to detect as
remote fs, added fs specific test since the actual mount name doesn't permit
reliable detection as remote type. Testing for trailing ':' isn't safe since
':' alone is not an invalid character in a file system name as far as I know.
Further, this exposed that the ^^ space replacements for $row[0] fs > 1 word
name were not being reset soon enough in the logic, that's also corrected.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Neglected to support standard package config file override
/etc/inxi.d/inxi.conf item. This is mainly useful for packaged inxi's who want
to override the distro maintainer /etc/inxi.conf file. Test priority is the same
except /etc/inxi.d/inxi.conf comes right after /etc/inxi.conf now in the test
sequence.
2. Added basic cygwin id, yes, inxi works in cygwin, apparently, with some
issues. Added cygwin os id to distro ids.
3. Added --version info for debugger, sometimes we want to know what verion of
a tool, like lspci, in case it has a bug or something.
4. Added exfat and apfs to unmounted fs types.
5. More disk vendors!! New vendor ID matches!! Yes, yes, you've heard it all
before, the list never ends!! The eternal chaos of existence manifested in just
how many IDs can be generated for new and old disk vendors alike!!!
--------------------------------------------------------------------------------
CHANGES:
1. No changes this release.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Pull request #253 corrected typos, urls, and other errors in man page,
inxi/pinxi comments, pinxi.1/inxi.1, README.txt, and updated LICENSE.txt to
current gnu wording.
--------------------------------------------------------------------------------
CODE:
1. Forgot to add lspci debugger fake data option, that's corrected. That's
--fake lspci, now works, didn't before, only the bsd pci tools had fake switches
previously, since lspci never needs debugging really, but did now to test an
issue report.
2. Added -CYGWIN to debugger file name. Added -ANDROID if ARM and if android.
3. With Fix 6, refactored entire lspci_data block, added lspci_n_data item,
which matches bus id of lspci -nnv when corruption occurs and replaces vendor,
product, and if also missing, rev version. I kind of knew I'd have to do this
fix one day, that was the same fix logic used on the BSD pci tools, which have
similar issues with consistency in output, or lack thereof.
This refactor is long term very good because it avoids an entire class of
possible errors, and makes pci detections far more robust.
4. Created new repo, for legacy code, inxi-legacy. Moved branch inxi-c to
inxi-legacy/xorg-c, moved branch xiin to /xiin, moved branch inxi-legacy (binxi)
to inxi-legacy/inxi-legacy. Those directories each contain all the files each
branch had in it.
This gets rid of some branches clutter, and nobody needs to see those anymore,
but if they care, they can look at them. Note that to do this, I had to merge
their histories, which was not that nice, but git is just really bad at this
type of stuff, so that's how it goes.
Times like this really make me miss svn's directory based branch approach...
5. Simplified sub fs_excludes, simplified regex constructors for all function
that use this data, made list more fault tolerate by adding global (fs)?(\d{0,2}
which means all file systems can have or not have 'fs' at end, and all can have
or not have a version number in string.
6. Exposed by issue #255, refactored slightly ordering of partition filter
logics and variable resets in the df output processing loop.
7. Added --fake partitions, to help debug odd corner cases like cygwin glitches.
2021-10-12 01:56:00 +00:00
|
|
|
\fB/etc/inxi.conf\fR file but don't want to lose your changes on a package
|
|
|
|
|
update.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
You can also override, per user, with a user configuration file found in one of
|
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
Some very nice issue reports have helped correct various corner case issues.
Mint users helped find a big one with lspci.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Unsure how to handle Android case where inxi correctly does -r test, see bug
3 fixes 6, but android incorrectly claims it is readable when it is not
readable, then the reader tool can't read the file and fails with permissions
error. This is one of those weird android errors that are pretty much impossible
to fully work around, but we can get rid of the readline() errors when reader()
was trying to work on a file handle that did not exist, that part was an inxi
bug.
--------------------------------------------------------------------------------
BUGS:
1. dm detection was not using case sensitive search for duplicates, leading to
cases where dm like slim / SLiM failed to get detected and then repeated in
output. Anonymous BSD debugger dataset exposed this issue, thanks.
2. In certain corner cases, like ARM Android, sub reader got passed a file that
had passed the is readable -r test, but it still failed with permissions error,
which then led reader to try to keep working with a null $fh. While in theory
nothing non readable should be passed to reader(), that fails when the OS fails
to actually follow correct readable rules, as in this case. Added protections in
reader() to handle this case, now will show error, but will not try to work with
$fh, that is how it should have been all along, but this is a very corner case.
Exposed by an anoymous ARM debugger dataset.
Thanks Termux user for creating the debugger dataset that exposed this issue.
3. lspci parser didn't null port value each iteration, resulting in all pci
items getting port values. Not a big deal, port is only used one place, but good
to find and correct that error.
4. Not an inxi bug, but would appear so to end users: lspsci -nnv implements a
truncating routine and breaks the first line for each bus id. See Fix 6 and Code
fix 3.
--------------------------------------------------------------------------------
FIXES:
1. -S and -I would show Console: tty pts/3 even though pts device is a pty, not
a tty. The only time this happened was when connecting to a remote system using
ssh or something like that. Local console still shows Console: tty 2 since that
was correct, but Console: tty pts/2 was confusing since technically it's not a
tty, it's a pty, pseudo terminal.
Now shows, when relevant: Console: tty 2 OR Console: pty pts/2.
2. Issue #252 notes that Emacs (and possibly other code/text editors with native
embedded terminals) includes a native virtual terminal that also follows
configuration rules from the editor to highlight trailing spaces. This created
odd looking screen output in Emacs vt mode since inxi always sets key/value
pairs with a white space ending as separator for next key value pair for screen
output mode, resulting always in a trailing space on each vt screen line. Fix
was to remove the last trailing space just prior to the print line point to
avoid this issue.
As a general thing, I'm curious to learn if any editor other than Emacs actually
contains its own virtual terminal that also follows the editor rules for output.
Or if any virtual terminal has such a highlight trailing space rule, which would
be imo so annoying it's hard to understand why a vt would implement it. Easy to
understand why Emacs (or any editor) does it, but an editor also being a vt AND
applying certain editor display configurations to the vt is a very specific and
unique circumstance I'd say.
Odd, historical, but there it is, why not handle it?
3. ARM / Android case where certain files passed the read -r test, but failed
with permission denied error. This tripped a further glitch where reader() would
then try to work with the failed $fh, see bug 2. This was really more a fix
than a bug, since the bug in this case was in android permissions tests, not
inxi, but it appears to be a bug to end users, so it's handled now.
4. Another ARM/Android, there was a voltage regulator IP that contained the term
wlan so it tripped false positive for network match. Added a new type,
regulator, to filter out those, like codec and dummy do already.
5. For issue #254, fix for cygwin ERR-102 in partitions, add cygwin test, new
dev type, 'windows', dev base then becomes E: or whatever. To avoid confusing D:
for a key: with no value, added D:/ slash.
6. Mint people discovered lspci issue, lspci -nnv has a bug where it will
truncate the output of the first line per bus ID if it's over some arbitrary
amount, then tack on rev and other items to end of that string, which leads to
the block: [vendorID:productID] getting truncated or removed altogether. Clearly
an oversight, at least I hope it's an oversight on lspci's part, but have to
work around the issue anyway since it may never get fixed, and has been around a
long time. Bug is in lspci 3.7, 3.6.4, and probably earlier.
Also added in a fillin tool for this rare case, lspci -n data is used to replace
the missing values.
Note that while lspci recommends using -mmv, for machine parsing, apparently
nobody noticed that -mmv doesn't have the same data items as -nnv, sigh.
7. Issue #255 noted that the combination of:
GoogleDrive Hogne: fuse.rclone 15728640
which is two word remote fs AND a fs type with a '.' in it would fail to trip
the handler for that multi word remote mount name. Also failed to detect as
remote fs, added fs specific test since the actual mount name doesn't permit
reliable detection as remote type. Testing for trailing ':' isn't safe since
':' alone is not an invalid character in a file system name as far as I know.
Further, this exposed that the ^^ space replacements for $row[0] fs > 1 word
name were not being reset soon enough in the logic, that's also corrected.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Neglected to support standard package config file override
/etc/inxi.d/inxi.conf item. This is mainly useful for packaged inxi's who want
to override the distro maintainer /etc/inxi.conf file. Test priority is the same
except /etc/inxi.d/inxi.conf comes right after /etc/inxi.conf now in the test
sequence.
2. Added basic cygwin id, yes, inxi works in cygwin, apparently, with some
issues. Added cygwin os id to distro ids.
3. Added --version info for debugger, sometimes we want to know what verion of
a tool, like lspci, in case it has a bug or something.
4. Added exfat and apfs to unmounted fs types.
5. More disk vendors!! New vendor ID matches!! Yes, yes, you've heard it all
before, the list never ends!! The eternal chaos of existence manifested in just
how many IDs can be generated for new and old disk vendors alike!!!
--------------------------------------------------------------------------------
CHANGES:
1. No changes this release.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Pull request #253 corrected typos, urls, and other errors in man page,
inxi/pinxi comments, pinxi.1/inxi.1, README.txt, and updated LICENSE.txt to
current gnu wording.
--------------------------------------------------------------------------------
CODE:
1. Forgot to add lspci debugger fake data option, that's corrected. That's
--fake lspci, now works, didn't before, only the bsd pci tools had fake switches
previously, since lspci never needs debugging really, but did now to test an
issue report.
2. Added -CYGWIN to debugger file name. Added -ANDROID if ARM and if android.
3. With Fix 6, refactored entire lspci_data block, added lspci_n_data item,
which matches bus id of lspci -nnv when corruption occurs and replaces vendor,
product, and if also missing, rev version. I kind of knew I'd have to do this
fix one day, that was the same fix logic used on the BSD pci tools, which have
similar issues with consistency in output, or lack thereof.
This refactor is long term very good because it avoids an entire class of
possible errors, and makes pci detections far more robust.
4. Created new repo, for legacy code, inxi-legacy. Moved branch inxi-c to
inxi-legacy/xorg-c, moved branch xiin to /xiin, moved branch inxi-legacy (binxi)
to inxi-legacy/inxi-legacy. Those directories each contain all the files each
branch had in it.
This gets rid of some branches clutter, and nobody needs to see those anymore,
but if they care, they can look at them. Note that to do this, I had to merge
their histories, which was not that nice, but git is just really bad at this
type of stuff, so that's how it goes.
Times like this really make me miss svn's directory based branch approach...
5. Simplified sub fs_excludes, simplified regex constructors for all function
that use this data, made list more fault tolerate by adding global (fs)?(\d{0,2}
which means all file systems can have or not have 'fs' at end, and all can have
or not have a version number in string.
6. Exposed by issue #255, refactored slightly ordering of partition filter
logics and variable resets in the df output processing loop.
7. Added --fake partitions, to help debug odd corner cases like cygwin glitches.
2021-10-12 01:56:00 +00:00
|
|
|
the following locations (inxi will store its config file using the following
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
precedence):
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
if \fB$XDG_CONFIG_HOME\fR is not empty, it will go there, else if
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fB$HOME/.config/inxi.conf\fR exists, it will go there, and as a last default,
|
2018-04-04 06:41:06 +00:00
|
|
|
the legacy location is used), i.e.:
|
New version, new tarball. This is a significant change, but inxi should handle it smoothly.
While default configs remain in /etc/inxi.conf, the user overrides now use the following order of tests:
1. XDG_CONFIG_HOME / XDG_DATA_HOME for the config and log/debugger data respectively.
2. Since those will often be blank, it then uses a second priority check:
$HOME/.config $HOME/.local/share to place the inxi data directory, which was previously here:
$HOME/.inxi
3. If neither of these cases are present, inxi will default to its legacy user data: $HOME/.inxi as before
In order to make this switch transparent to users, inxi will move the files from .inxi to the respective
.config/ .local/share/inxi directories, and remove the .inxi directory after to cleanup.
Also, since I was fixing some path stuff, I also did issue 77, manual inxi install not putting man pages in
/usr/local/share/man/man1, which had caused an issue with Arch linux inxi installer. Note that I can't help
users who had a manual inxi install with their man page in /usr/share/man/man1 already, because it's too risky
to guess about user or system intentions, this man location correction will only apply if users have never
installed inxi before manually, and have no distro version installed, unlike the config/data directory,
which does update neatly with output letting users know the data was moved.
Note that if users have man --path set up incorrectly, it's possible that the legacy man page would show up
instead, which isn't good, but there was no perfect fix for the man issue so I just picked the easiest way,
ignoring all man pages installed into /usr/share/man/man1 and treating them as final location, otherwise
using if present the /usr/local/share/man/man1 location for new manual install users.
Also, for users with existing man locations and an inxi manually installed, you have to update to inxi current,
then move your man file to /usr/local/share/man/man1, then update man with: mandb command (as root), after that
inxi will update to the new man location.
Also added some more XDG debugger data as well to cover this for future debugger data.
This closes previous issue #77 (man page for manual inxi install does not go into /usr/local/share/man/man1) and
issue 101, which I made today just to force the update.
Just as a side note, I find this absurd attempt at 'simplifying by making more complex and convoluted' re the XDG
and .config and standard nix . file to be sort of tragic, because really, they've just made it all way more complicated,
and since all 3 methods can be present, all the stuff has to be tested for anyway, so this doesn't make matters cleaner
at all, it's just pointless busywork that makes some people happy since now there's even more rules to follow, sigh.
2016-12-20 02:57:56 +00:00
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fB$XDG_CONFIG_HOME/inxi.conf\fR > \fB$HOME/.config/inxi.conf\fR >
|
|
|
|
|
\fB$HOME/.inxi/inxi.conf\fR > \fB/etc/inxi.d/inxi.conf\fR > \fB/etc/inxi.conf\fR
|
New version, new tarball. This is a significant change, but inxi should handle it smoothly.
While default configs remain in /etc/inxi.conf, the user overrides now use the following order of tests:
1. XDG_CONFIG_HOME / XDG_DATA_HOME for the config and log/debugger data respectively.
2. Since those will often be blank, it then uses a second priority check:
$HOME/.config $HOME/.local/share to place the inxi data directory, which was previously here:
$HOME/.inxi
3. If neither of these cases are present, inxi will default to its legacy user data: $HOME/.inxi as before
In order to make this switch transparent to users, inxi will move the files from .inxi to the respective
.config/ .local/share/inxi directories, and remove the .inxi directory after to cleanup.
Also, since I was fixing some path stuff, I also did issue 77, manual inxi install not putting man pages in
/usr/local/share/man/man1, which had caused an issue with Arch linux inxi installer. Note that I can't help
users who had a manual inxi install with their man page in /usr/share/man/man1 already, because it's too risky
to guess about user or system intentions, this man location correction will only apply if users have never
installed inxi before manually, and have no distro version installed, unlike the config/data directory,
which does update neatly with output letting users know the data was moved.
Note that if users have man --path set up incorrectly, it's possible that the legacy man page would show up
instead, which isn't good, but there was no perfect fix for the man issue so I just picked the easiest way,
ignoring all man pages installed into /usr/share/man/man1 and treating them as final location, otherwise
using if present the /usr/local/share/man/man1 location for new manual install users.
Also, for users with existing man locations and an inxi manually installed, you have to update to inxi current,
then move your man file to /usr/local/share/man/man1, then update man with: mandb command (as root), after that
inxi will update to the new man location.
Also added some more XDG debugger data as well to cover this for future debugger data.
This closes previous issue #77 (man page for manual inxi install does not go into /usr/local/share/man/man1) and
issue 101, which I made today just to force the update.
Just as a side note, I find this absurd attempt at 'simplifying by making more complex and convoluted' re the XDG
and .config and standard nix . file to be sort of tragic, because really, they've just made it all way more complicated,
and since all 3 methods can be present, all the stuff has to be tested for anyway, so this doesn't make matters cleaner
at all, it's just pointless busywork that makes some people happy since now there's even more rules to follow, sigh.
2016-12-20 02:57:56 +00:00
|
|
|
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
.SH CONFIGURATION OPTIONS
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
See the documentation page for more complete information on how to set
|
2018-04-04 06:41:06 +00:00
|
|
|
these up, and for a complete list of options:
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
2017-09-22 00:12:58 +00:00
|
|
|
.I https://smxi.org/docs/inxi\-configuration.htm
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B Basic Options
|
2018-04-06 22:52:08 +00:00
|
|
|
Here's a brief overview of the basic options you are likely to want to use:
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBCOLS_MAX_CONSOLE\fR The max display column width on terminal. If
|
|
|
|
|
terminal/console width or \fB\-\-width\fR is less than wrap width, wrapping of
|
|
|
|
|
line starter occurs
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBCOLS_MAX_IRC\fR The max display column width on IRC clients.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBCOLS_MAX_NO_DISPLAY\fR The max display column width in out of X / Wayland /
|
|
|
|
|
desktop / window manager.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBCPU_SLEEP\fR Decimal value \fB0\fR or more. Default is usually around
|
|
|
|
|
\fB0.35\fR seconds. Time that inxi will 'sleep' before getting CPU speed data,
|
|
|
|
|
so that it reflects actual system state.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
\fBDOWNLOADER\fR Sets default inxi downloader: curl, fetch, ftp, perl, wget.
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
See \fB\-\-recommends\fR output for more information on downloaders and Perl
|
|
|
|
|
downloaders.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBFILTER_STRING\fR Default \fB<filter>\fR. Any string you prefer to see
|
|
|
|
|
instead for filtered values.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBINDENT\fR Change primary indent width of wide mode output. See
|
|
|
|
|
\fB\-\-indent\fR.
|
|
|
|
|
|
|
|
|
|
\fBINDENTS\fR Change primary indents of narrow wrapped mode output, and second
|
|
|
|
|
level indents. See \fB\-\-indents\fR.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBLIMIT\fR Overrides default of \fB10\fR IP addresses per IF. This is only of
|
|
|
|
|
interest to sys admins running servers with many IP addresses.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
\fBLINES_MAX\fR Values: [\-2\-xxx]. See \fB\-Y\fR for explanation and values.
|
|
|
|
|
Use \fB\-Y \-3\fR to restore default unlimited output lines. Avoid using this in
|
|
|
|
|
general unless the machine is a headless system and you want the output to be
|
|
|
|
|
always controlled.
|
|
|
|
|
|
|
|
|
|
\fBMAX_WRAP\fR (or \fBWRAP_MAX\fR) The maximum width where the line starter
|
|
|
|
|
wraps to its own line. If terminal/console width or \fB\-\-width\fR is less than
|
|
|
|
|
wrap width, wrapping of line starter occurs. Overrides default. See
|
|
|
|
|
\fB\-\-max\-wrap\fR. If \fB80\fR or less, wrap will never happen.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBNO_DIG\fR Set to \fB1\fR or \fBtrue\fR to disable WAN IP use of \fBdig\fR
|
|
|
|
|
and force use of alternate downloaders.
|
New inxi, new man. Huge update, new line types, huge graphics upgrade, new
switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!!
Note that since this features a new primary line item (-j / --swap Swap:),
the version number has been bumped to 3.1.0, making this a major version
upgrade, the first since the new Perl inxi rewrite was launched, though of
course 3.0.0 contained many new line items as well, but this is the first
actually new line item since then.
Bugs:
1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME
directory, the partitions would buggily duplicate in the output.
2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver
because it was using the wrong Xorg log, it was only searcing in the original
/var/log/Xorg.0.log file, not the newer alternative path locations.
Fixes:
1. Both an enhancement and a fix, users reported Xorg log file location changes.
Fix is that now inxi uses wildcard searches of all readable locations that can
contain the log files, then collects a list of them, and uses the last modified
one. This ensures that the best possible guess is made about which actual
log file is current, which should lead to significantly more reliable Xorg
driver reports overall.
Note that this fix works for user level and root level, it will always use the
most recent readable file no matter what. For root, that should translate to
the most recent on an absolute level Xorg log file. This issue was caused by
gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and
also, the location is often but not always now:
~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why
root has to search for all user Xorg log files to find the most recent one.
There were many red-herrings in this issue report, so it took some research to
dig through those to the real data sources.
2. Now that the compositor detection is out of early testing mode, enabled
always on compositor detection for Wayland systems. Since the compositor
is the Wayland display server, it makes sense to always show it if Wayland.
Note that there is still no known way to actually reliably get Wayland data
beyond simple environmental variables that let inxi detect Wayland is running
the desktop. Lack of reliable logs or debugging tools across Wayland compositors
makes this entire process about 10-50x more difficult than it should have been.
3. In keeping with 2., also moved compositor: item to be right after server:
item.
4. Debian bug:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi
requested that HTTP::Tiny be set to default always check SSL certificates.
Now inxi does that, and --no-ssl flag disables this, which makes the Perl
http downloader now work roughly the same as wget, curl, etc.
5. Man page fixes, added pointer placeholders for out of alphabetical order
options, so you can find anything by looking down the alpha sorted lists, like:
--swap - See -j. Since inxi is running out of single letters that match new
features, it's easier to point man readers to the right item without them
having to already know it to find it. Also added --dbg [2-xx] pointer to
github inxi-perl/docs/inxi-values.txt so people interested can learn how to
trip the various per feature screen debuggers.
Enhancements:
1. updated ubuntu ids, added 'focal LTS'.
2. USB Graphic devices added. This will add support for USB graphics adapters,
an uncommon but existing category, often used in SOC boards, for example, but
also on desktops, and things like USB webcams. Leaving these off was really
just an oversight, the programming internally had the data, it just wasn't
using it.
3. Support added for TV card type multimedia devices in Graphics. That was
actually a long term oversight, I'd simply missed that in the device ID
documentation, one of the multimedia device subtypes is Video device.
4. Huge, massive, internal upgrade to allow for -Ga output, which gives a
technically accurate Xorg > Display > Screen > Monitor breakdown. Note that
Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr,
but if xrandr is missing, the Screen information shows.
Technically for -G, -Gxx, end users see very little difference except the per
Screen / per Monitor resolutions are listed with a 1: type counter per item.
Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs
out of the pieces of hardware that make up the Screen space. In many cases,
1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty
different.
New output items:
Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg
Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]]
Screen-x: [Screen number]; s-res: [Xorg Screen resolution];
s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size;
s-diag: [diagonal of Xorg Screen size]
Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions];
hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated
from actual monitor resolution/size; size: [actual monitor size in mm (inch);
diag: [actual diagonal size in mm (inch).
4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution
section for -G.
5. Big improvement in error messages and logging for Xorg driver detections,
this logic is much more robust now, but after the main driver fix, also much less
likely to ever be seen.
6. Almost not visible to users, but major internal graphics refactor allows now
for more modular treatment, and eventual Wayland data sourcing. Currently
most Wayland data sourcing is in stub form, or only logically possible, but
as it grows possible (if ever, since Wayland protocal appears to have totally
neglected enforcing single location logging, and single tool debugging for
the entire Wayland protocol of compositors, a massive oversight in my view).
The -Ga refactors internally made this much more possible, and I integrated
switches and tests, and fallbacks, and stubs in some locations, so it was
clear where current Xorg specific logic is, and where future Wayland logic
will fit in, sort of anyway.
7. Debugger tools added for new features, or most of them.
8. New primary line item: --swap / -j. This moves all swap data to a dedicated
Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap
is used, all swap types, not only physical partition swaps, show. This should
make some users happy.
9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later
Intel cpu family ids in terms of cpu arch name tool.
10. By request, added ability filter out all UUID or Partition Label
strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and
--filter-uuid. Mostly useful in fringe cases, for example, replacing
label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>,
or in cases you want to show full -v8 output without showing UUID or Labels,
whatever.
11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables
dig in cases where dig is installed but failed due to maybe network firewall
rules or something, and WAN IP detection fails. Normally you always want
to use dig, it's faster, more reliable, and safer, than all the other regular
downloader based methods, but we have seen server setups where for some reason
those types of dig requests were blocked, thus disabling WAN IP detection.
12. Added in WAN IP failure case, if dig was used, suggestion to try
again with --no-dig, since most users are unlikely to learn about this issue,
or the solution to it.
13. Added single letter shortcut -J for --usb, maybe this will help people
discover usb component of inxi, now you can request for instance: inxi -FJaz
14. Added xonsh to supported shells, that had tripped a perl undefined value
for start client bug since xonsh uses single word for version, xonsh/234
so the default value, 2nd word, was undefined.
15. More SSD and USB drive vendors from the endless fountain over at
Linux Hardware Database (linuxliteos.com).
Changes:
1. Small change in how screen resolutions are output in -G non -a mode,
now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key.
This helps make it more readable. Note that in non -a mode, the increments
are just based on Screen, then Monitor, Monitor, Screen, and so on, counts.
Most users will only have one Screen systems, but more advanced setups may use
the Xorg > 1 Screen, each screen able to run > 1 monitors.
The counts in say, a 2 Screen system, with 3 monitors, would be:
1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2]
3: res3 [from screen 1, monitor 1.
If xrandr is not installed, it would show:
1: res1 [from screen 0] 2: res2 [from screen 1]
2020-04-23 02:35:53 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBNO_DOAS\fR Set to \fB1\fR or \fBtrue\fR to disable internal use of
|
|
|
|
|
\fBdoas\fR.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBNO_HTML_WAN\fR Set to \fB1\fR or \fBtrue\fR to disable WAN IP use of
|
|
|
|
|
\fBHTML Downloaders\fR and force use of dig only, or nothing if dig disabled
|
|
|
|
|
as well. Same as \fB\-\-no\-html\-wan\fR. Only use if dig is failing, and
|
|
|
|
|
HTML downloaders are hanging.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBNO_SUDO\fR Set to \fB1\fR or \fBtrue\fR to disable internal use of
|
|
|
|
|
\fBsudo\fR.
|
New version, man page, exciting changes!!
Bugs:
1. issue #200 - forgot to add all variants for -p, now works with --partition-full
and --partitions-full
2. issue #199 - another one, forgot to add --disk to -D for long version. Thanks
adrian15 for both of these, he was testing something and discovered these were
missing.
3. Issue #187 an issue with RAID syntax not being handled in a certain case,
thanks EnochTheWise for following through on this one. This turned out to be
a bad copy paste, a test pattern did not match the match pattern.
Fixes:
1. Fixed some docs typos.
2. Issue #188 fixed protections and filters for some glxinfo output handlers.
3. Issue #195, for Elbrus bit detection.
4. Added filter to cpu data, was not skipping if arm, so Model string
was treated numerically.
Enhancements:
1. Added rescatux to Debian system base detections. This closes issue #202, again
from adrian15, thanks.
2. For cpu architecture, updated for latest AMD ryzen and other families, like
Zen 3, which is just coming out re available data. Also latest Intel, which are
trickier to ID right now, but I think I got the latest ones right,
That's things like coffee lake, amber lake, comet lake, etc.
3. Huge one, full (hopefully out of the box) Russian Elbrus CPU support. Thanks
to the alt-linux and the others who helped provide data and feedback to get support.
Note that this was also part of correcting 64 bit detection for e2k type, which
is how Elbrus IDs internally. See issue #197 which I've left open for the time
being for more information on this CPU and how it's now handled by inxi.
Note all available data should now work for Elbrus, including physical cpu/core
counts etc. Elbrus do not show flag information, nor do they use min/max speed,
so that data isn't available, but everything else seems to work well.
4. Eternal disk vendors. Thanks linux lite hardware database, you continue to
help make the disk vendor feature work by supplying every known vendor ever seen.
5. To close debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942194
Note that the fix is simply to give the user the option to disable this behavior
with the new --no-sudo and NO_SUDO configuration file options. This issue should
never have been filed as a bug since even the poster admitted it was a wishlist
item, but because of how debian bug tracker works, it's hard to get rid of
invalid bugs. Note that this is the internal use of sudo for hddtemp and file,
not starting inxi with sudo, so using this option or configuration item just
removes sudo from the command. Note that because the user did not do as
requested, and never actually filed a github wishlist issue, and since his
request was vague and basically pointless, the fix is just to let you switch
off sudo, that's all.
2019-11-20 04:42:21 +00:00
|
|
|
|
New version, new man. Huge set of changes. Excitement!! Thrills! Spills?
Bugs:
1. There was a missing main::is_int test that in some instances triggered
error. This is corrected.
2. More of a fix, but legacy devices were not matching NIC to IF because
the /sys path was not a link as it is now. I made a separate function to
handle that match test so it could be more readily be worked with.
Fixes:
1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why?
who knows. That to me is a bug, but since if it's not handled in inxi, it makes
it look like inxi has a server: -G bug, I worked around it. Again. This creates
the bug when you do not use the actual true path of Xorg where Xorg.wrapper
complains and will not show -version data. Why move this? why use that wrapper
thing? I don't know, makes no sense to me.
2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though
it will certainly need more work.
3. Better ARM support, added in devicetree strings, which helps pad out the
Devices IDs, albeit with very little data, but at least the devices are detected.
Thanks Manjaro ARM people there again.
4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS
device totally puke and die, killed networking, so since very few upstart running
systems will be arm/mips devices, I decided there better safe than sorry.
5. Found another uptime syntax case, MIPS as root does not have the users item.
6. Many tweaks to SOC data generators, will catch more categories, but the lists
will never be done since each device can be, and often is, random re the syntax.
7. USB networking failed to test usb type for 'network', which led to failed
ids on some device strings. SOC types are now filtered through a function
to create consistent device type strings for the per device tool to use to
assign each to its proper @device_<type> array.
8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and
trailing subsubclass values, this converts it into the same hex 4 item string
that is used by GNU/Linux/lspci so I can apply consistent rules to all pci
types, no matter what the generator source is, lspci, pcidump, pciconf, and
eventually pcictl if I can get netbsd running.
9. Fixed internal --dbg counts for various features, and updated docs for that.
10. Fixed ARM / MIPS missing data messages, they were redundant.
11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt.
12. Added unity-system-compositor as mir detection, who knew? I guess that was
its production application name all along? Oh well.
Enhancements:
1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough
to make errors not happen.-repos
2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non
BSD unix.
3. Added S6 init system to init tool.
4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required>
message on Device-x: lines if not root. All working.
5. Fully refactored the old pci stuff to DeviceData package/class, due to adding
so many types to that, it made sense to make it a single class.
6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense
to integrate the data grabber into one package/class
7. Added speed: item to USB:, it shows in Mb/s or Gb/s
8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the
devices data logic into DeviceData.
9. Added ash shell, not sure if that detection will work, but if it does, it will
show.
10. As part of the overall DeviceData refactor, I moved all per type data into
dedicated arrays, like @device_graphics, @device_audio, @device_network, etc,
which lets me totally dump all the per device item tests, and just check the
arrays, which have already been tested for on the construction of the primary
DeviceData set. Moved all per type detections into DeviceData so that is now
one complete logic block, and the per type data generators don't need to know
about any of that logic at all anymore.
11. Added sway, swaybar, way-cooler as window managers, info items. Not 100%
positive about the --version, their docs weren't very consistent, but I think
the guess should be right if their docs weren't incorrect.
12. Added vendor: item to network, not sure why I kept that off when I added
vendor: to audio and graphics. It made sense at the time, but not now, so now
-GNA all have vendor: if detected.
13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware
database, somehow you have users that manage to use every obscure usb/ssd/hdd
known to humanity.
14. Big update to --admin, now has the following:
A: partitions: shows 'raw size: ' of partition, this lets users see the amount
of file system overhead, along with the available size as usual.
B: partitions: show percent of raw in size:
C: partitions: show if root, block size of partition file system. Uses
blockdev --getbsz <part>
D: partition: swap: show swappiness and vfs cache pressure, with (default)
or (default <default value) added. This apparently can help debugging some
kernel issues etc. Whatever, I'll take someone's word for that.
E: Disks: show block size: logical: physical:
15. New option and configuration item: --partition-sort / PARTITION_SORT
This lets users change default mount point sort order to any available ordering
in the partition item. Man page and help menu show options.
16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses
an immensely stripped down busybox (no ps aux, for example), maybe because it
only runs as root user/ not sure, anyway, took many fixes.
Changes:
1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number,
like 3.1. Note that this is going to be wrong for BSDs, but that's fine.
2. Changed slightly the output of Memory item, now it follows the following rules:
A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory:
item, which makes sense. Note that -m overrides all other options of where Memory
minireport could be located.
B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm
C: if -I is triggered, and -m is not triggered, Memory: shows in -I line.
D: no change in short form inxi no arg output, Memory is there.
2018-09-24 23:50:33 +00:00
|
|
|
\fBPARTITION_SORT\fR Overrides default partition output sort. See
|
|
|
|
|
\fB\-\-partition\-sort\fR for options.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBPS_COUNT\fR The default number of items showing per \fB\-t\fR type, \fBm\fR
|
|
|
|
|
or \fBc\fR. Default is 5.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBSENSORS_CPU_NO\fR In cases of ambiguous temp1/temp2 (inxi can't figure out
|
2021-08-25 03:39:33 +00:00
|
|
|
which is the CPU), forces sensors to use either value 1 or 2 as CPU
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
temperature. See the above configuration page on smxi.org for full info.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBSENSORS_EXCLUDE\fR Exclude supplied sensor array[s] from sensor output.
|
|
|
|
|
Override with \fB\-\-sensors\-default\fR. See \fB\-\-sensors\-exclude\fR.
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
|
|
|
|
|
\fBSENSORS_USE\fR Use only supplied sensor array[s]. Override with
|
|
|
|
|
\fB\-\-sensors\-default\fR. See \fB\-\-sensors\-use\fR.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fBSEP2_CONSOLE\fR Replaces default key / value separator of '\fB:\fR'. Test
|
|
|
|
|
with \fB\-\-separator\fR.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
New version, man page. Big set of changes. Full USB refactor, plus added features.
Bugs:
1. A result of the issue #156 USB refactor, I discovered that the --usb sort order,
which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed
by using a second USB hub on a bus, the Device IDs are not really related in any
clearly logical way to the actual position on the bus. The solution was to fully
refactor the entire USB logic and then use generated alpha sorters based on the full
bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1.
Note that Device IDs start at 1 for each bus, regardless of how many hubs you have
attached to that port.
2. Certain situations triggered a bug in Optical devices, I'd forgotten to change
$_ to $key in two places. Since that part didn't normally get triggered, I'd never
noticed that bug before. Thanks TinyCore for exposing that glitch!
Fixes:
1. On legacy systems, fluxbox --version does not work, -v does. Corrected.
2. for --usb, network devices should now show the correct 'type: Network'.
For some weird reason, the people who made the usb types didn't seem to consider
many key devices, scanners, wifi/ethernet adapters, and those are almost always
"Vendor defined class".
3. A really big fix, for instances where system is using only Busybox, like
TinyCore, or booting into any system running busybox for whatever reason, now
avoids the various errors when using busybox ps, which only for example outputs
3, not 11, default columns for ps aux, and which does not support ps -j, which
is used in the start/shell client information. This gets rid of a huge spray
of errors, and actually allows for pretty complete output from systems that only
have busybox tools installed. This should cover everything from TinyCore to MIPS
to ARM systems that run minimalist Linux. Note that this fix goes along with the
/sys based USB parser, since such systems may have USB, but are unlikely to have
lsusb installed, but do have /sys USB data.
4. In some cases, strings /sbin/init would trigger a false version result, fixed
that logic so now it rarely will do that.
Enhancements:
1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile
window manager (no version info).
2. Added Bodhi detection; Salix + base slackware; kde neon system base;
3. Added support for slaptget repos, basic, it may not be perfecct.
4. More disk vendors, and matches for existing vendors.
5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines.
This makes lsusb optional, though recommended (because it has a better vendor/
product ID to string internal database) than /sys data. This was in response
to a second set of issues in #156 by gm10, USB drivers.
Depending on the system, using only /sys data, while slightly less informative,
is between 20 and 2000 milliseconds faster, so if you want speed, either use the
new --usb-sys option, or the configuration file USB_SYS=[true|false] option.
1. switched to cleaner more efficient data structures
2. added ports count to hub report, linux and bsd.
3. added [--usb|-A|-N] -xxx serial for Device items, if present.
4. added --usb -xx drivers, per interface, can be 1 or more drivers.
5. fully refactored -A and -N usb device logic, far cleaner and simple now,
much easier to work with, no more hacks to find things and match them.
6. USB type: now comes from /sys, and is in general going to be more accurate
than the lsusb -v based method, which was always an ugly and incomplete hack.
As with drivers, it also now lists all the interface types found per device, not
just the first one as with the previous method. Note that HID means the more
verbose: Human Interface Device, but I shortened it. Now that the type: data is
created by inxi reading the class/subclass/protocal IDs, and then figuring out
what to do itself, I can have quite a bit more flexibility in terms of how type
is generated.
7. added --usb -xxx interfaces: [count] for devices, which lists the device
interface count. This can be useful to determine if say, a usb/keyboard adapter
is a 2 interface device. Note that Audio devices generally have many interfaces,
since they do more than 1 thing (audio output, microphone input, etc.).
8. Support for user configuration file item: USB_SYS=[true|false]. This is useful
if you want to see only the /sys version of the data, or if you want the significant
speed boost not using lsusb offers, particularly on older systems with a complex
USB setup, many buses, many devices, etc.
New option --usb-tool overrides USB_SYS value, and forces lsusb use.
9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb.
Note that you still have to use the feature options, like --usb, -A, or -N. This
can lead to a significant improvement in execution time for inxi.
10. Rather than the previous bus:device ID string, to go along with the internal
sorting strings used, inxi now shows the real Bus / port /port ids, like:
1-3.2.1:3 - Bus-Port[.port]:device id.
6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore!
7. Added tce package manager to repos. That's the tinycore package manager.
Changes:
1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been
replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint
in issue #156
This makes sense because for a long time, most of these devices are not cards, they
are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are
some form of a device, and the one thing that they are all not is a Card. Along with
the recent change from HDD: to Local Storage in Disks: this brings inxi terminology
out of the ancient times and into the present. Thanks for the nudge gm10.
Removed:
See inxi-perl/docs/inxi-fragments.txt for removed blocks.
1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux
and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete
the lsusb vendor/product strings.
2. Two functions that were used by -A and -N to match usb devices and get their /sys data,
that became redundant since it all now goes through the /sys parser already, so those
features can get the data pre-parsed from the @usb arrays.
Output Examples:
Sort by DeviceID failures in 3.0.20 using Device ID:
inxi --usb
USB:
Hub: 1:1 usb: 2.0 type: Full speed (or root) hub
Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse
Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard
Device-3: Verbatim bus ID: 1:11 type: Mass Storage
Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13
type: Vendor Specific Class
Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub
Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86
type: Audio
Device-6: Canon CanoScan LiDE 110 bus ID: 1:112
type: Vendor Specific Protocol
Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113
type: Mass Storage
Hub: 2:1 usb: 3.1 type: Full speed (or root) hub
Hub: 3:1 usb: 2.0 type: Full speed (or root) hub
Hub: 4:1 usb: 3.1 type: Full speed (or root) hub
Hub: 5:1 usb: 2.0 type: Full speed (or root) hub
Hub: 6:1 usb: 3.0 type: Full speed (or root) hub
Corrected: sort by BusID in 3.0.21:
inxi --usb
USB:
Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14
Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4
Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID bus ID: 1-3.2:86
Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage
bus ID: 1-3.4:113
Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2
Device-4: Verbatim type: Mass Storage bus ID: 1-7:11
Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3
Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112
Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13
Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8
Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2
Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2
Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4
Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4
2018-08-17 22:58:44 +00:00
|
|
|
\fBUSB_SYS\fR Forces all USB data to use \fB/sys\fR instead of \fBlsusb\fR.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBWAN_IP_URL\fR Forces \fB\-i\fR to use supplied URL, and to not use dig
|
|
|
|
|
(dig is generally much faster). URL must begin with http or ftp. Note that if
|
|
|
|
|
you use this, the downloader set tests will run each time you start inxi
|
|
|
|
|
whether a downloader feature is going to be used or not.
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
The IP address from the URL must be the last item on the last (non\-empty)
|
|
|
|
|
line of the URL's page content source code.
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
|
|
|
|
|
Same as \fB\-\-wan\-ip\-url [URL]\fR
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBWEATHER_SOURCE\fR Values: [\fB0-9\fR]. Same as \fB\-\-weather\-source\fR.
|
|
|
|
|
Values 4\-9 are not currently supported, but this can change at any time.
|
New version, new man page. Big update! Get it in before your freeze!!
Bugs:
1. Maybe the vendor/product regex, which when + was used, would put out
errors.
2. Maybe Fix 4, since that could lead to incorrect behavior when sudo
is involved depending on sudo configuration.
3. BIG: current inxi weather will probably fail if not updated to this or
newer versions!! Not an inxi bug per se, but your users will see it as one.
Fixes:
1. Fixed Patriot disk ID.
2. Fixes for PPC board handling.
3. Regex cleaner fixes, this could lead to error in special cases of product
vendor names.
4. crazy from frugalware pointed out that $b_root detection was flawed, and
relied on a bad assumption, particularly for sudo. As usual, he's right, that
is now corrected, and uses $< Perl native to determine UID.
Enhancements:
1. Added septor to Debian system base.
2. Removed quiet filters for downloaders when using --dbg 1, now you see the
entire download action for curl/wget downloads. This went along with
issue # 174
3. New feature: --wan-ip-url. This closed issue #174. Also has user config
option: WAN_IP_URL as well to make changes permanent.
4. Added --dbg 1 to man and help. The other --dbg options are random and can
change, but --dbg 1 is always for downloading, so might as well tell people
about it.
5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org
based robust API. This also allows for a new switch, --weather-source (or --ws
for shorter version), options 0-9, which will trigger different APIs on smxi.org.
Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not
currently active. Also added in better error handling for weather.
The main benefit here is that inxi is now largely agnostic to the weather APIs
used, and those can be changed with no impact to inxi users who are running
frozen pool inxi's, or who have not updated their inxi versions.
NOTE: all inxi versions older than 3.0.31 will probably fail for weather
quite soon. So update your inxi version in your repos!!
6. More disk vendors IDs and matches. Thanks linuxlite hardware database.
7. Going along with weather changes, added, if present, cloud cover, rain, and
snow reports. Those are for previously observed hour.
8. Small change to Intel CPU architecture, taking a guess on stepping for
skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But
could not find this documented, so it's a guess. At worst, it means that Cascade
lake, which must be a later steppingi than 4, will not be ID'ed as skylake.
9. Documentation updates for data sources.
Changes:
1. inxi now uses a new system to get weather data. There is no longer a risk
of weather failing if the API used locally in inxi fails or goes away. This
change should be largely invisible to casual users.
2. In weather, moved dewpoint to be after humidity, which makes a little more
sense.
2019-02-07 02:31:55 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBWEATHER_UNIT\fR Values: [\fBm\fR|\fBi\fR|\fBmi\fR|\fBim\fR]. Same as
|
|
|
|
|
\fB\-\-weather\-unit\fR.
|
New version, new man. Bug fixes, feature updates.
The main reason to release this earlier than I had hoped was because of the /sys
permission change for serial/uuid file data. The earlier we can get this fix out,
the better for end users, otherwise they will think they have no serial data when
they really do.
FIXES:
1. this bug just came to my attention, apparently the (I assume) kernel people
decided for us that we don't need to see our serial numbers in /sys unless we are
root. This is an unfortunate but sadly predictable event. To work around this
recent change (somewhere between 4.14 and 4.15 as far as I can tell), inxi -M and
-B now check for root read-only and show <root required> if the file exists but
is not user readable. I wish, I really wish, that people could stop changing stuff
for no good reason, but that's out of my control, all I can do is adjust inxi to
this reality. But shame on whoever decided that was a good idea.
This is not technically an inxi bug, but rather a regression, since it's caused
by a change in /sys permissions, but users would see it as a bug so I consider
this an important fix.
Note that the new /sys/class/dmi/id permissions result in various possible things:
1. serial/uuid file is empty but exists and is not readable by user
2. serial/uuid file is not empty and exists and is not readable by user
3. serial/uuid file does not exist
4. serial/uuid file exists, is not empty, and is readable by root
Does this change make your life better? It doesn't make mine better, it makes
it worse. Consider filing a bug report against whoever allowed this regression
is my suggestion.
BUGS:
1. A weather bug could result in odd or wrong data showing in weather output, this
was due to a mistake in how the weather data was assembled internally. This error
could lead to large datastore files, and odd output that is not all correct.
2. More of an enhancement, but due to the way 'v' is used in version numbers,
the program_version tool in some cases could have sliced out a 'v' in the wrong
place in the version string, and also could have sliced out legitimate v values.
This v issue also appeared in bios version, so now the new rule for program_version
and certain other version results is to trim off starting v if and only if it is
followed by a number.
FEATURES:
1. Added in OpenBSD support for showing machine data without having to use dmidecode.
This is a combination of systcl -a and dmesg.boot data, not very good quality data
sources, but it is available as user, and it does work. Note that BIOS systems
are the only ones tested, I don't know what the syntax for UEFI is for the field
names and strings. Coming soon is Battery and Sensors data, from the same sources.
Sadly as far as I know, OpenBSD is the only BSD that has such nice, usable (well,
ok, dmesg.boot data is low quality strings, not really machine safe) data. I
have no new datasets from the other BSDs so I don't know if they have decided to
copy/emulate this method.
2. By request, and this was listed in issue #134, item no. 1, added in weather
switchable metric/imperial output. Also added an option, --weather-unit and
configuration item: WEATHER_UNIT with possible values: cf|fc|c|f. The 2nd of
two in cf/fc goes in () in the output. Note that windspeed is m/s or km/h as metric,
inxi shows m/s as default for metric and (km/h as secondary). Also fixed -w
observation date to use local time formatting. That does not work in -W so it shows
the default value.
3. Updated man to show new WEATHER_UNIT config option, and new --weather-unit
option. Also fixed some other small man glitches that I had missed.
2018-05-11 20:53:26 +00:00
|
|
|
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.TP
|
|
|
|
|
.B Color Options
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
It's best to use the \fB\-c [94\-99]\fR color selector tool to set the
|
|
|
|
|
following values because it will correctly update the configuration file and
|
|
|
|
|
remove any invalid or conflicting items, but if you prefer to create your own
|
|
|
|
|
configuration files, here are the options. All take the integer value from the
|
|
|
|
|
options available in \fB\-c 94\-99\fR.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
NOTE: All default and configuration file set color values are removed when
|
|
|
|
|
output is piped or redirected. You must use the explicit
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fB\-c [color number]\fR option if you want colors to be present in the
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
piped/redirected output (creating a PDF for example).
|
New version, man page. Fixes, enhancements, changes.
Thanks:
1. AntiX forums, for testing -C --admin, suggestions, always helpful.
Bugs:
1. Added switch to set @ps_gui, I forgot case where info block was only thing
that used ps_gui (Nitrux kde nomad latte case). This led to no info: data if
other ps_gui switches not activated. Now each block that can use it activates it.
Fixes:
1. To clarify issue #161 added help/man explanation on how to get colors in cases
where you want to preserve colors for piped or redirected output. Thanks fugo.
2. LMDE 3.0 released, slightly different system base handling, so refactored to
add Debian version, see enhancement 2. Tested on some old vm instances, improved
old system Debian system base id, but it's empirical, distro by distro, there is
no rule I can use to automatically do it, sadly.
3. 'Motherboard' sensors field name added, a few small tweaks to sensors. This
was in response to issue #159, which also raised a problem I was not really
aware of, user generated sensor config files, that can have totally random
field names. Longer term solution, start getting data from sys to pad out
lm-sensors data, or to handle cases where no lm-sensors installed.
4. Fixed kwin_11 and kwin_wayland compositor print names, I'd left out the _,
which made it look strange, like there were two compositors or something.
5. Fixed latte-dock ID, I thought the program name when running was latte, not
latte-dock. inxi checks for both now. Thanks Nitrux for exposing that in vm test.
6. Sensors: added in a small filter to motherboard temp, avoid values that are
too high, like SYSTIN: 118 C, filters out to only use < 90 C. Very unlikely a
mobo would be more than 90C unless it's a mistake or about to melt. This may
correct anoymous debugger dataset report from rakasunka.
Enhancements:
1. Added --admin to -v 8 and to --debugger 2x
2. Expanded system base to use Debian version tool, like the ubuntu one, that
lets me match version number to codename. The ubuntu one matches code names to
release dates. Added Neptune, PureOS, Sparky, Tails, to new Debian system base
handler.
3. Big enhancement: --admin -C now shows a nice report on cpu vulnerabilities,
and has a good error message if no data found. Report shows:
Vulnerabilities: Type: [e.g. meltdown] status/mitigation: text explanation.
Note: 'status' is for when no mitigation, either not applicable, or is vulnerable.
'mitigation' is when it's handled, and how. Thanks issue #160 Vascom from Fedora
for that request.
4. The never-ending saga of disk vendor IDs continues. More obscure vendors,
more matches to existing vendors. Thanks linuxlite/linux hardware database
Changes:
1. Reordered usb output, I don't know why I had Hubs and Devices use different
ordering and different -x switch priorities, that was silly, and made it hard to
read.
Now shows:
Device/Hub: bus-id-port-id[.port-id]:device-id info: [product info]
type/ports: [devices/hubs] usb: [type, speed]
-x adds drivers for devices, and usb: speed is now default for devices, same as
Hubs. Why I had those different is beyond me.
The USB ordering is now more sensible, the various components of each
matching whether hub or device.
Unfixable or Won't Fix:
1. Unable to detect Nomad desktop. As far as I can tell, Nomad is only a theme
applied to KDE Plasma, there is no program by that name detectable, only a
reference in ps aux to a theme called nomad.
2. Nitrux system base ID will not work until they correct their /etc/os-release file.
3. Tails live cd for some inexplicable reason uses non standard /etc/os-release
field names, which forces me to either do a custom detection just for them, or for
them to fix this bug. I opted for ignoring it, if I let each distro break standard
formats then try to work around it, the distro ID will grow to be a 1000 lines long
easily. Will file distro bug reports when I find these from now on.
Samples:
This shows the corrected, cleaned up, consistent usb output:
inxi -y80 --usb
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID usb: 1.1
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse usb: 1.1
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse usb: 1.1
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
usb: 2.0
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network usb: 2.0
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
inxi -y80 --usb -xxxz
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0
chip ID: 1d6b:0002
Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1 chip ID: 03eb:0902
Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk)
type: Audio,HID driver: cm109,snd-usb-audio interfaces: 4 usb: 1.1
chip ID: 0d8c:000e
Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse driver: usbhid,wacom
interfaces: 1 usb: 1.1 chip ID: 056a:0011
Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse
driver: hid-generic,usbhid interfaces: 2 usb: 1.1 chip ID: 0d3d:0001
Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific>
driver: N/A interfaces: 1 usb: 2.0 chip ID: 04a9:1909
Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network
driver: asix interfaces: 1 usb: 2.0 chip ID: 05ac:1402 serial: <filter>
Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1
chip ID: 1d6b:0003
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0
chip ID: 1d6b:0002
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1
chip ID: 1d6b:0003
Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0
chip ID: 1d6b:0002
Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0
chip ID: 1d6b:0003
2018-09-07 20:58:55 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBCONSOLE_COLOR_SCHEME\fR The color scheme for console output (not in
|
|
|
|
|
X/Wayland).
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
New version, new man. Beta / 2.9 testing completed.
inxi 3.0 is now ready for prime time. No substantial issues have been found over
the past week. All outstanding issues and bugs have been corrected. The man page
and help page have been edited fairly heavily to improve usability and readablity.
All work and development and support for inxi 2.3.56 is ended. No issues for
2.3.56 will be accepted since there is no way to support that version, it
being in a different set of languages (Gawk/Bash) than inxi 2.9/3.0 (Perl 5).
So the sooner you move your distro package pool to new inxi, the sooner your
users can get support for any issues with current inxi.
Beta and 2.9 prerelease testing is completed, and has resulted in a much
better inxi than I could have hoped for.
There are so many new features and enhancements in the new inxi that it's hard
to list them all. See previous commits for a more in depth record.
1. New options: --slots (PCI Slots); --usb
2. Exports to json/xml with --output options
3. Every line has been enhanced, with tighter output control, better key / value
pairings, more accurate values.
4. Line wrapping is now fully dynamic, which means inxi works down to 80 columns
and should basically never wrap (except for very long repo lines, but that's not
really fixable).
5. More controls, more user configuration options (see man page).
6. So many small new features that it's hard to list them all. Shows SSH in -I
if SSH. Shows sudo/su/login in -I if relevant and detectable. Shows disk partioning
scheme in some cases (more coming). Removes color codes if piped or redirected to
file.
7. All sizes are now shown in standardized KiB/MiB/GiB/TiB/PiB format, to avoid
ambiguity about whether M or MB or MiB is meant. All internal size math is done
using KiB, which further avoids confusion and error. Note that many disk makers
like using MB or GB instead of MiB or GiB because it makes their disks seem
'bigger'.
8. Sensors -s now supports IPMI sensors, in tandem with lm-sensors.
Anyway, the changelog will show better all the new features etc, I can't remember
them all.
All current issues and glitches have been fixed, any remaining are simply new issues,
just as they would be in old inxi.
Note that in the second and third weeks of beta testing a significant number of bugs
that are in inxi 2.3.56 were fixed. 2.3.56 has been moth-balled into the inxi-legacy
branch as binxi, to avoid mixing it up with inxi. The development branch is now
permanently inxi-perl, aka, pinxi, since that worked so well for beta and pre-3.0
2.9 testing and development.
This ends the pinxi/inxi development stage. All future development will proceed
using the inxi-perl branch, and will be the same in terms of new features as pre
inxi 2.9 was, they will be added, enhanced, as seems appropriate.
Remember, inxi is a rolling release program, like Arch Linux, Gentoo, Debian
Testing/Sid, and has no frozen release points, so this is simply the beginning of the
3.0 line of Perl inxi.
Thanks to everyone who contributed time, energy, effort, ideas, testing, debugging,
patience - inxi would not work without you.
2018-04-09 08:24:47 +00:00
|
|
|
\fBGLOBAL_COLOR_SCHEME\fR Overrides all other color schemes.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
|
|
|
|
\fBIRC_COLOR_SCHEME\fR Desktop X/Wayland IRC CLI color scheme.
|
|
|
|
|
|
|
|
|
|
\fBIRC_CONS_COLOR_SCHEME\fR Out of X/Wayland, IRC CLI color scheme.
|
|
|
|
|
|
|
|
|
|
\fBIRC_X_TERM_COLOR_SCHEME\fR In X/Wayland IRC client terminal color scheme.
|
|
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
\fBVIRT_TERM_COLOR_SCHEME\fR Color scheme for virtual terminal output (in
|
|
|
|
|
X/Wayland).
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
.TP
|
|
|
|
|
.B Developer Options
|
|
|
|
|
These are useful only for developers.
|
|
|
|
|
|
Bug release, replace 3.3.17 asap, most users will not experience the bug, but if
they do, inxi stops right before the -D line. Failed to do an if defined test on
an array ref that could be undefined or an array ref. That makes Perl very
unhappy!
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. AMD family F, K8 series, will need more granular treatments to get the data
to be more accurate and less generic. We got 2 IDs nailed from raw visual data
confirmations and cpuid values, which leaves many, but good start. We will chip
away (pardon the pun) at these more ambiguous IDs over time, but don't need to
get them all done instantly, just eventually. Thanks slackware person linuxdaddy
for doing really good research and actually looking at the cpu to find dates
etc.
--------------------------------------------------------------------------------
BUGS:
1. Bug, fatal, caused by internal hash/array ref refactor of 3.3.17. Thanks
alaymari github issue #271 for reporting this one.
--------------------------------------------------------------------------------
FIXES:
1. None except for code fixes to try to avoid the cause of the bug in Bugs 1.
2. Fixed nvidia eol try --gpu, it was showing backwards, with --gpu, not
without, sigh.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added slimski dm data. That's a new fork of SLiM. Also guessing that brzdm
has same version -v output: brzdm version x.xx
--------------------------------------------------------------------------------
CHANGES:
1. None
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Refactors of core docs, ongoing, but will list those next release.
--------------------------------------------------------------------------------
CODE:
1. Cleaned up some array ref handling in subs, returned as: ($var1,$var2) =
@{block_data(...)}, skipped initializing and creating scalar to hold the ref,
just use it directly for DiskItem::block_data().
2. Also switched to local ref scalar array in DiskItem::scsi_data(),
DiskItem::block_data(). Not set local array, set local array ref, to keep it
clear. Also made DriveItem::drive_speed() return straight ref, not array then
ref. Same for many other subs, switched to ref assignment so it's the same ref
all through all the sub and return.
3. Fixed a redundant return \@$data to simply assinging to @$data ref, no return
needed, in DiskItem::smartctl_data().
4. Tightened some returns of ref so that tests if good test @$ref, not $ref.
Trying to avoid more cases like issue #271.
5. Going along with array ref local/return, switched all hash refs to local hash
ref returning ref, and working local with ref. More efficient, avoids creating
new refs over and over, dugh. This made a particularly large difference in CPU
because in certain parts, new references were being created over and over, and
subs were returning like \@arr or \%hash instead of declaring to start:
my $arr = []; my $hash = {};
Then working with the data from there on as an array or hash reference, to the
same original reference, rather than creating new ones over and over, which Perl
then has to track til they expire.
2022-06-13 23:32:32 +00:00
|
|
|
\fBFAKE_DATA_DIR\fR \- change default fake data directory location. See
|
Rollout of advanced microarchitecture info continues, added AMD/Intel gfx
devices, CPU built dates, process nodes, generation (in some cases, where it
makes sense), etc.
Please note: the 3.3.16 > 17 releases require manual matching table updates. If
you think disk or ram vendor, CPU or GPU process, release date, generation, etc,
information is not correct:
* FIRST: do the research, confirm it's wrong, using wikichips, techpowerup,
wikipedia links, but also be aware, sometimes these slightly contradict each-
other, so research. Don't make me do all your work for you.
* Show the relelevant data, like cpu model/stepping, to correct the issue, or
model name string.
* There are 4 main manually updated matching tables, which use either raw regex
to generate the match based on the model name (ram, disk vendors), or vendor id
matching (ram vendors), product id matching (gpu data), or cpu family / model /
stepping id matching. Each of these has its own matching tool at:
inxi-perl/tools/[tool-name].pl
which is used to generate either raw data used by the functions (ids for gpu
data), or which contains the master copy of the function used to generate the
regex matches (cp_cpu_arch/set_ram_vendors/set_disk_vendors).
* Please use pinxi and inxi-perl branch for this data, inxi is only released
when next stable is done, all development is done in inxi-perl branch. All
development for the data or functions these tools are made for occurs in the
tools, not in pinxi, and those results are moved into pinxi from the tools.
* Saying something "doesn't work" is not helpful, provide the required data for
the feature that needs updating, or ideally, find the correct answer yourself
and do the research and then provide the updated data for matching.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. GPU/CPU process node sizes are marketing, not engineering, terms, but
work-around is to list the fab too so you at least know which set of marketing
terms you're dealing with. As of around 7nm, most of the fabs are not using nm
in their names anymore, TSMC is using n7, Intel 7, for example. While these
marketing terms do reflect changes from the previous process node, more
efficient, faster, faster per watt, and so on, and these changes are often quite
significant, 10-30%, or more, they do not reflect the size of the transistor
gate like they used to up until about 350nm. Intel will move to A20 for the node
after 4 or 5, 2nm, meaning 20 angstroms.
Intel suggested million transistors per mm^2 as an objective measure (currently
around 300+ million!! as of ~7nm), but TSMC didn't take them up on it.
GlobalFoundries (GF) stepped away from these ultra small processes at around
14nm, so you won't see GF very often in the data. AMD spun off its chip fabs to
GF aound 2009, so you don't see AMD as foundry after GF was formed. ATI always
used TSMC so GPU data for AMD/ATI is I think all TSMC. Intel has always been its
own foundry.
2. Wayland drops all its data and can't be detected if sudo or su is used to run
inxi. That's unfortunate, but goes along with their dropping support for > 1
user, which was one of the points of wayland, same reason you can do desktop
sharing or ssh desktop forwarding etc. This means inxi doesn't show wayland as
Display protocol, it is just blank, if you use su, or sudo start. This makes
some internal inxi wayland triggers then fail. Still looking to see if there is
a fix or workaround for this.
3. In sensors, a new syntax for k10-pci temp, Tctl, which unfortunately is the
only temp type present for AMD family 17h (zen) and newer cpus, but that is not
an actual cpu temp, it's:
https://www.kernel.org/doc/html/v5.12/hwmon/k10temp.html
"Tctl is the processor temperature control value, used by the platform to
control cooling systems. Tctl is a non-physical temperature on an arbitrary
scale measured in degrees. It does _not_ represent an actual physical
temperature like die or case temperature."
Even worse, it replaced Tdie, which was, correctly, temp1_input, and, somewhat
insanely, the non real cpu temp is now temp1_input, and if present, the real
Tdie cpu temp is temp2_input. I don't know how to work around this problem.
--------------------------------------------------------------------------------
BUGS:
1. Fallback test for Intel cpu arch was not doing anything, used wrong variable
name.
2. A very old bug, thanks mrmazda for spotting this one, runlevel in case of
init 3 > init 5 showed 35, not 5. Doesn't show on systemd stuff often since it
doesn't use runlevels in this way, but this bug has been around a really long
time.
3. SensorItem::gpu_data was always logging its data, missing the if $b_log.
--------------------------------------------------------------------------------
FIXES:
1. Fixed some disk vendor detection rules.
2. Failing to return default target for systemd/systemctl when no:
/etc/systemd/system/default.target
file exists. Corrected to use systemctl get-default as fallback if file doesn't
exist.
3. Fixed indentation for default: runlevel, should be child of runlevel: /
target:
4. Fixed corner case where systemd has no /proc/1/comm file but is still the
init system. Added fallback check for /run/systemd/units, if that exists, safe
to assume systemd is running init.
5. Fixed subtle case, -h/--recommends/--version/--version-short should not print
to -y1 width, but rather to the original or modified widths >= 80 cols.
Corrected this in print_basic() by using max-cols-basic.
6. Forgot to add --pkg, --edid, and --gpu to debugger run_self() tool.
7. Fixed broken sandisk vendor id.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added AMD and Intel GPU microarchitecture detections for -Gx. These are not
as easy as Nvidia because there is no one reliable data source for product ids.
2. Going with the -Ga process: .. built: item, -Ca will show process: [node] and
built: years and sometimes gen: if available. Geeky, sure, not always perfect,
or correct, but will generally be close. Due to difficultly in finding reliable
release > build end years for example, not all cpus have all this data.
Using CPU generation,where that data is available and makes sense. Like AMD
Zen+ is zen gen: 2, for example,. Because Intel microarch names are often
marketing driven, not engineering, it's too difficult to assign gen consistently
based only on model names. Shows for Core intels like: gen: core 3
That will cover most consumer Intel CPU users currently.
3. Added initial Zen 3+ and Zen 4 ids for cp_cpu_arch(). There is very little
info on these yet, so I'm going on what may prove to be incomplete or wrong
data.
4. Added GPU process, build years for -Ga.
5. Added fallback test for gpus that we don't have product IDs for yet because
dbs have not been updated. Only used for cases where it's the newest gpu series
and no prodoct IDs have been found.
6. Added AMD am386 support to cp_cpu_arch... ok ok, inxi takes 9 minutes to
execute on that, but there you have it.
7. Added unverified Hyprland wayland compositor detection.
8. By request, added --version-short/--vs, which outputs version info in one
line if used together with other options and if not short form. With any normal
line option, will output version (date) info first line, without any other
option, will output 1 line version info and exit.
9. More disk vendors, ids! Much easier with new tool disk_vendors.pl.
--------------------------------------------------------------------------------
CHANGES:
1. Deprecated --nvidia/--nv in favor of more consistent --gpu, that's easier to
work with multiple vendors for advanced gpu architecture. Note for non nvidia,
--gpu only adds codename, if available and different from arch name. For nvidia,
it adds a lot more data.
2. Changed inxi-perl/tools tool names to more clearly reflect what function they
serve.
3. Going with runlevel fixes, changed 'runlevel:' to be 'target:' if systemd.
Also changed incorrect 'target:' for 'default:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man, help, docs/inxi-data.txt for new gpu data and tools, and to
indicate switch to more generic --gpu trigger for advanced gpu data, instead of
the now deprecated --nvidia/--nv, which probably will go down as the shortest
lasting option documented, though of course inxi always keeps legacy syntax
working, behind the scenes, it's just removed from the -h and man page in favor
of --gpu. Also updated to show AMD/Intel/Nvidia now, since the data now roughly
works for all three main gpus.
2. Updated pinxi README.txt to reflect the tools and how to use them and what
they are for.
3. --help, man, updated for target/runlevel, default: changes for init data.
4. Updated configuration html and man for --fake-data-dir.
--------------------------------------------------------------------------------
CODE:
1. Upgraded tools/gpu_ids.pl to handle nvidia, intel, or amd data, added data
files in tools/lists/ for amd. First changed name from ids.pl to gpu_ids.pl
2. New data files added for amd/intel pci ids, and a new tool to merge them and
prep them for gpu_ids.pl -j amd|intel handling. All work. Took a while to get
these things sorted, but don't want to get stuck in future with manual updates,
it needs to be automated as much as possible, same as with disk_vendors.pl etc,
if I'm going to try to maintain this over time.
3. Made all gpu data file names use consistent formats, and made disk data files
also follow this format.
4. Changed raw_ids.pl to gpu_raw.pl, trying to keep things easy to remember and
consistent here.
5. Refactored core gpu data logic, now all types use the same sub, and just
assign various data depending on the type.
6. Changed vendors.pl name to disk_vendors.pl
7. Big redo of array/hash handling in OutputHandler, was partially by reference,
now is completely by reference. All Items now use and return $rows array ref as
well, from start to finish, unlike previously, where @rows was copied
repeatedly.
8. Going along with 7, made most internal passing of hash/arrays use hash/array
references instead, where it makes sense, and doesn't make the code harder to
work with.
9. Refactored WeatherItem, split apart the parts from output to be more like
normal Items in terms of error handling etc.
10. Added 'ref' return option for reader() and grabber(). Only useful for very
large data sets, added also default 'arr' if no value is provided for that
argument.
11. Switched some features to use grabber/reader by ref on the off chance that
will dump some execution time.
12. A few places added qr/.../ precompiled regex, in simple form, for loops,
maybe it helps a little. I don't know.
13. Added global $fake_data_dir, this can be changed via configuration item:
FAKE_DATA_DIR or one time by --fake-data-dir.
14. Created data directory, and initial data items. cpu is the fake data used to
test CPU info. More will be added as data is checked and sanitized.
2022-06-10 19:40:18 +00:00
|
|
|
\fB\-\-fake\-data\-dir\fR.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
.SH BUGS
|
|
|
|
|
Please report bugs using the following resources.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
You may be asked to run the inxi debugger tool (see \fB\-\-debug 21/22\fR),
|
|
|
|
|
which will upload a data dump of system files for use in debugging inxi. These
|
|
|
|
|
data dumps are very important since they provide us with all the real system
|
|
|
|
|
data inxi uses to parse out its report.
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
.B Issue Report
|
|
|
|
|
File an issue report:
|
2023-09-18 00:42:36 +00:00
|
|
|
.I https://codeberg.org/smxi/inxi/issues
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
New features, new changes, new bug fixes!!! Excitement!!! Thrills!!!
Bugs:
1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank,
only inxi short, which I rarely use so I didn't notice.
2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed.
Also failed to test for null data, so showed errors for packages as well. Both
fixed.
3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME
drives do NOT follow the age old /proc/partitions logic where if the minor number is
divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not
a partition. nvme drives use a random numbering when > 1 nvme drives are present, and
the old tests would fail for all nvme drivers more than the first one, which led
to wrong disk size totals. Thanks gardotd426 who took the time to help figure this
out in issue #223 - fix is to not do that test for nvme drives, or rather, to add
a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor
number.
Fixes:
1. Corrected indentation for block sizes, children were not indented.
2. Updated some older inxi-perl/docs pages, why not, once in a while?
3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been
corrected, and the kernel gcc version now shows correctly for the previous
syntax and the new one. Hopefully they do not change it again, sigh...
4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and
are also usually not board/cpu sensors, but things like ath10, iwl, etc,
network, or disk sensors, etc. In some cases hwmon sensor data would appear
Enhancements:
1. Big sensors refactor, now inxi supports two new sensors options:
--sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that
in the refactored logic, and in the old logic, gpu sensors were already excluded.
Now other hardware specific sensors like network are excluded as well.
--sensors-use - use ONLY list of supplied sensor IDs, which have to match the
syntax you see in lm-sensors sensors output.
Both accept comma separated list of sensors, 1 or more, no spaces.
The refactor however is more far reaching, now inxi stores and structures data
not as a long line of sensors and data without differentiation, but by sensor array/chip
ID, which is how the exclude and use features can work, and how granular default
hardware sensor exclusions and uses can happen. This is now working in the gpu
sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk
temperature sensors values, which will lead in some cases to being able to get
sensors data for disks without root or hddtemp. This is a complicated bit of logic,
and I don't have time to do it right now, but the data is now there and stored
and possible to use in the future.
To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data
and its structures, which makes debugger a lot easier for new features.
This issue was originally generated by what was in my view an invalid complaint
about some inxi sensors defaults, which led me to look more closely at sensors
logic, which is severely lacking. More work on sensors will happen in the future,
time, health, and energy permitting.
2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor
data will be added as new data samples show what will be available for the
free modules like amdgpu, nouvean, and the intel graphics modules.
3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended,
so statement remains true. Thanks linux-lite hardware database.
Changes:
1. This has always bugged me since it was introduced, the primary cpu line starter
Topology: which was only technically accurate for its direct value, not its children,
and also, in -b, cpu short form was using the value as the key, which is a no-no,
I'd been meaning to fix that too, but finally realized if I just make the primary
CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both
problems.
To keep the -b cpu line as short as before, I removed the 'type:' and integraged
that value into the primary Info: string:
CPU:
Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz
-b 3.1.05 and earlier:
CPU:
6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz
These resolve something that has irked me for quite a while, 'Topology:' didn't
fit, it was too geeky, and worst, it only applied to the value directly following
it, NOT to the rest of the CPU information. It also could not be shortened or
abbreviated since then it would have made no actual sense, like topo:, and the
same issue with value being used for key in -b, and wrong word for line starter
in -C would have existed. Besides, someone might think I was trying to make a
subtle reference to the great Jodorowsky film 'El Topo', which would be silly,
because that's art, and this is just some system specs that are reasonably
readable...
2. Was using opendns for WAN dig IP address, but apparently cysco bought that
company, and now I've noticed the old opendns dig queries were failing more and
more, so replaced that with akamai dig requests.
Also made the WAN IP fallback to HTTP IP method if dig failed. New option:
--no-http-wan and config item NO_HTTP_WAN with override --http-wan added to
let you switch off http wan IP requests if you want. Note that if dig fails,
you will get no wan ip address.
Updated/improved error messages to handle this more complex set of wan ip
options, so hopefully the error alert message will in most cases be right.
3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming
from the old techpatterns.com/incoming. Updated man/help to remove those urls too.
2020-08-16 22:27:11 +00:00
|
|
|
.B Forums
|
|
|
|
|
Post on inxi forums:
|
|
|
|
|
.I https://techpatterns.com/forums/forum\-33.html
|
2012-09-15 09:18:08 +00:00
|
|
|
.TP
|
A small point release, mainly to get some bug fixes, and a few minor issues, and
some ongoing updates to various matching rule features like CPU, Disk Vendors,
etc.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. mrmazda, for continuing to poke around and finding oddities on occasion.
2. The various packagers, for continuing to package inxi.
3. Nothing else really comes to mind, so I'm thankful that no real issues popped
up, and the ongoing attempt to stabilize and clean up the several year
aggressive development cycle of code is proceeding quite well.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. I'm currently getting no data samples from new server type CPU systems,
Nvidia Grace, Ampere, both ARM V2 based. The ARM cpu arch logic hasn't been
updated in many years since I have gotten no meaningful data, currently
Raspberry Pi 4 is the latest ARM generation I've seen data for, and no ARM
server type for many years. So support there is really not happening, and won't
be until I start getting real datasets on those server systems.
Nvidia uses Neoverse V2 ARM core, but I have no information on that yet. Also
nothing from the Amazon CPU, new Marvell datacenter type CPUs. But that's not
surprising.Also, nothing from the N1 (2019) or V1 Neoverse (2021) ARM CPU family
even though those have now been out a while.
A lot of the advanced CPU data should 'just work' because of the huge CPU
refactor done recently, but some of the more advanced data, particularly
cpu_arch type data, isn't going to be available until I get real data sets so I
can see what's going on. No idea how CPUID might work for ARM cpus, for example.
Objectively many of these datacenter/machine learning focused CPUs will never
see a system inxi will run on, though most I suspect will be running GNU/Linux
in some form, so inxi can in theory run on them, but those people all know what
their systems are doing, so the need isn't particularly pressing of course.
With this said, I did used to have more access to cutting edge server stuff, but
that has largely dried up, particularly ARM based chips.
--------------------------------------------------------------------------------
BUGS:
1. Found while resolving Fix 2, it turns out > 1 X Screens would not have shown
correctly due to failing to pass $j row counter by reference. This bug was
introduced when the big Monitor updates were done, since you almost never see
> 1 X Screens now, I never saw it until testing something for another reason.
This led to > 1 Screen showing on the same line as the last monitor of the
previous Screen.
See also Fixes 2, 3, 4, and Code 1, 2, 3.
--------------------------------------------------------------------------------
FIXES:
1. Changed Intel Saphire Rapids release data from 2021+ (what Intel had
initially announced) to 2023+ (the actual release date). Not my fault!! They
were too optimistic, inxi merely repeated their claims.
2. While trying to figure out extra Screen showing up, found a series of subtle
issues with how X Screens are handled. Added in more robust test for if Screen
ID has been added by xdpyinfo_data, and other weird corner cases that might
cause strange results in Display Screen-x.
Created check_screen() to allow for more granular and debugable testing.
This forum post helped focus attention on this issue:
https://forum.endeavouros.com/t/\
my-second-screen-is-not-working-after-installing-nvidia/33388
3. %monitors was not correctly assigned in xrandr screen fallback.
4. Set number of Screens found if no xdpyinfo or if xrandr found > xdpyinfo
number of screens.
5. Added Zhaoxin match to Centaur match, might show up on cpu string.
6. OpenBSD's package manager was listed as pkg_info, but it's slightly more
accurate to call it pkg_add. As far as I understand it, OpenBSD doesn't really
have a 'package manager' per se, it has a suite of tools to manage packages.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added some Zhaoxin/Centaur IDs, unlikely to show up, but you never know.
2. Added m68k to X display driver list. This was just added to kernel as a full
drm driver! Very legacy, but has users in vm, qemu, etc.
3. More disk vendors! I skipped updating this last time because, well,
collecting the data is really boring, and slightly tedious, and really serves to
simply remind that this is not the way towards a better world. Or are cheap SSDs
the true path after all? I doubt it, but you never know.
4. New AMD, Nvidia gpu ids.
5. New Intel Cpu Microarch IDs.
--------------------------------------------------------------------------------
CHANGES:
1. No changes to speak of, so I won't.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Various ongoing updates to inxi-perl/docs. These are very slowly being pulled
into a more useful form. Emphasis on slowly.
--------------------------------------------------------------------------------
CODE:
1. In Graphics::xdpyinfo_data() and Graphics::xrandr_data() got rid of extra
step, now just assign hash reference directly to push anonymous hash reference
into array. Had used intermidiate variable assignement of hash ref, but that is
pointless.
2. Added $fake{'xdpyinfo'}, hoping to get some debugger data to test weird
extra 'Screen' seen with Endeavor user (see Fix 2, 3, Bug 1).
3. Also, instead of using \%monitors, which creates a reference to the last
value of %monitors, used the correct and safer {%monitors}, which creates an
anonymous reference of the value %monitors had at that moment. This is a subtle
Perl error which is easy to make in cases where the hash or array reference is
almsot never > 1 instance, such as > 1 X Screens.
This should at least help resolve the repeated 'monitors' rows in the output
in Fixes 2, 3, 4.
4. Added 'source' to $graphics{'screens'} to log where each detected screen came
from, xdpyinfo or xrandr.
2022-12-11 00:04:04 +00:00
|
|
|
.B IRC irc.oftc.net\fR / \fBirc.libera.chat\fR
|
|
|
|
|
You can also visit \fRchannel:\fI #smxi\fR to post issues on either network.
|
New version, man page. Features, bugs, fixes!
Bugs:
1. Color selector accepted '' as a value, which it would then write to config
file, creating errors since it's not an integer value.
2. Corrected distro id error for last fallback case, making the distro ID out
of the filename itself, that was missing the assignment to $distro.
3. mmcblk0 was showing up as an unmounted partition, due to failing to filter
mmcblk[0-9] in unmounted.
Fixes:
1. Added missing compositor kwin_wayland to compositor detections
2. For -M, on laptops, sometimes Type: would duplicate in Chassis: type: which
looks silly, so now it checks to make sure the two values are different before
using the Chassis: type: data.
3. -D disk vendor, added GALAX, fixed Toshiba, which sometimes occurs other than
start of disk id string, so now it checks the whole string. This seems particularly
common in nvme devices from Toshiba. This is the only vendor I have found that
puts the vendor string later in the device id string.
4. Added protection against unreadable but present /etc/issue. This was caused
by a now fixed bug in OpenSuSe, which symbolically linked to create /etc/issue
from /var/run/issue, but with 600 permissions, root read only, that is. Note that
this bug has since been fixed (now has the correct 644 permissions), but I figured
better safe than sorry in case anyone else decides that's a good idea in the future.
Now only sends to reader if readable.
5. Related to 4, made reader not exit on failure, now just prints error message and
keeps going.
6. Upped maximum distro string length to 60, from 50. AntiX for example was coming
in at 48, so I decided to add some safe room now that inxi does dynamic sizing, it
is not a big problem having very long distro id strings.
Enhancements:
1. Added basic /proc data parser to debugger. Can't get all the data or files because
it's simply too big, but grabs the basics.
2. Added vcgencmd for some ARM rasberry pi debugging.
3. ARM: add model if not found in /proc/cpuinfo, or if different.
4. Added Tdie cpu sensor type, this is coming soon in latest kernels, so catching
it early. Tdie will replace k10-temp sensor item temp1.
5. Added --admin extra data option, and first set of extra data, -C, which will
show CPU Errata (bugs), family, model-id, stepping (as hex (decimal) or hex if less
than or equal to 9), microcode (as hex).
6. Battery: added with -x option, if found, attached battery driven devices, like
wifi keyboard, mouse. If upower is present, will also try to show battery charge
percent for those devices. Note that -B only shows the Device-X items if -x is used,
and will not show anything in -F unless there is a system, not device, battery
present, or if -Fx is used and there is a Device battery detected.
Added upower to recommends.
7. Basic -Dxxx disk rotation speeds added. Requires udevadm. Not all spinning disks
show rotation speeds, and it depends on udevadm, so if no rotation found, it shows
nothing.
8. Added explicit Arco Linux and Antergos distro ID support. This requires more
checks, but in theory, both should now show Arco Linux or Antergos instead of default
'Arch Linux' as before, plus extra data if found, like version.
2018-06-05 00:24:53 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH HOMEPAGE
|
2023-09-18 00:42:36 +00:00
|
|
|
.I https://codeberg.org/smxi/inxi
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
\fR \- Home of the source code, and tech docs
|
A small point release, mainly to get some bug fixes, and a few minor issues, and
some ongoing updates to various matching rule features like CPU, Disk Vendors,
etc.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. mrmazda, for continuing to poke around and finding oddities on occasion.
2. The various packagers, for continuing to package inxi.
3. Nothing else really comes to mind, so I'm thankful that no real issues popped
up, and the ongoing attempt to stabilize and clean up the several year
aggressive development cycle of code is proceeding quite well.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. I'm currently getting no data samples from new server type CPU systems,
Nvidia Grace, Ampere, both ARM V2 based. The ARM cpu arch logic hasn't been
updated in many years since I have gotten no meaningful data, currently
Raspberry Pi 4 is the latest ARM generation I've seen data for, and no ARM
server type for many years. So support there is really not happening, and won't
be until I start getting real datasets on those server systems.
Nvidia uses Neoverse V2 ARM core, but I have no information on that yet. Also
nothing from the Amazon CPU, new Marvell datacenter type CPUs. But that's not
surprising.Also, nothing from the N1 (2019) or V1 Neoverse (2021) ARM CPU family
even though those have now been out a while.
A lot of the advanced CPU data should 'just work' because of the huge CPU
refactor done recently, but some of the more advanced data, particularly
cpu_arch type data, isn't going to be available until I get real data sets so I
can see what's going on. No idea how CPUID might work for ARM cpus, for example.
Objectively many of these datacenter/machine learning focused CPUs will never
see a system inxi will run on, though most I suspect will be running GNU/Linux
in some form, so inxi can in theory run on them, but those people all know what
their systems are doing, so the need isn't particularly pressing of course.
With this said, I did used to have more access to cutting edge server stuff, but
that has largely dried up, particularly ARM based chips.
--------------------------------------------------------------------------------
BUGS:
1. Found while resolving Fix 2, it turns out > 1 X Screens would not have shown
correctly due to failing to pass $j row counter by reference. This bug was
introduced when the big Monitor updates were done, since you almost never see
> 1 X Screens now, I never saw it until testing something for another reason.
This led to > 1 Screen showing on the same line as the last monitor of the
previous Screen.
See also Fixes 2, 3, 4, and Code 1, 2, 3.
--------------------------------------------------------------------------------
FIXES:
1. Changed Intel Saphire Rapids release data from 2021+ (what Intel had
initially announced) to 2023+ (the actual release date). Not my fault!! They
were too optimistic, inxi merely repeated their claims.
2. While trying to figure out extra Screen showing up, found a series of subtle
issues with how X Screens are handled. Added in more robust test for if Screen
ID has been added by xdpyinfo_data, and other weird corner cases that might
cause strange results in Display Screen-x.
Created check_screen() to allow for more granular and debugable testing.
This forum post helped focus attention on this issue:
https://forum.endeavouros.com/t/\
my-second-screen-is-not-working-after-installing-nvidia/33388
3. %monitors was not correctly assigned in xrandr screen fallback.
4. Set number of Screens found if no xdpyinfo or if xrandr found > xdpyinfo
number of screens.
5. Added Zhaoxin match to Centaur match, might show up on cpu string.
6. OpenBSD's package manager was listed as pkg_info, but it's slightly more
accurate to call it pkg_add. As far as I understand it, OpenBSD doesn't really
have a 'package manager' per se, it has a suite of tools to manage packages.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added some Zhaoxin/Centaur IDs, unlikely to show up, but you never know.
2. Added m68k to X display driver list. This was just added to kernel as a full
drm driver! Very legacy, but has users in vm, qemu, etc.
3. More disk vendors! I skipped updating this last time because, well,
collecting the data is really boring, and slightly tedious, and really serves to
simply remind that this is not the way towards a better world. Or are cheap SSDs
the true path after all? I doubt it, but you never know.
4. New AMD, Nvidia gpu ids.
5. New Intel Cpu Microarch IDs.
--------------------------------------------------------------------------------
CHANGES:
1. No changes to speak of, so I won't.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Various ongoing updates to inxi-perl/docs. These are very slowly being pulled
into a more useful form. Emphasis on slowly.
--------------------------------------------------------------------------------
CODE:
1. In Graphics::xdpyinfo_data() and Graphics::xrandr_data() got rid of extra
step, now just assign hash reference directly to push anonymous hash reference
into array. Had used intermidiate variable assignement of hash ref, but that is
pointless.
2. Added $fake{'xdpyinfo'}, hoping to get some debugger data to test weird
extra 'Screen' seen with Endeavor user (see Fix 2, 3, Bug 1).
3. Also, instead of using \%monitors, which creates a reference to the last
value of %monitors, used the correct and safer {%monitors}, which creates an
anonymous reference of the value %monitors had at that moment. This is a subtle
Perl error which is easy to make in cases where the hash or array reference is
almsot never > 1 instance, such as > 1 X Screens.
This should at least help resolve the repeated 'monitors' rows in the output
in Fixes 2, 3, 4.
4. Added 'source' to $graphics{'screens'} to log where each detected screen came
from, xdpyinfo or xrandr.
2022-12-11 00:04:04 +00:00
|
|
|
(\fIinxi\-perl/docs\fR).
|
New version, new man. Fixes, stitches, and returns!!
Bugs:
1. As a fix (3), failure to handle spaces in mount source names. More of a fix than
a bug, since it was an old issue #63.
2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data
tripping null data or unreadable file errors, but I'll call those bugs since they
look like bugs to end users. See Fixes for more.
3. See Fix 4, this is sort of a bug, inxi failed to return expected values on
success/failure.
Fixes:
1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented
internally. This is now corrected.
2. Apple OSX was returning errors, those were fixed.
3. Finally handled ancient issue #63, support now there for spaces in remote source
name. This means that both spaces in source block name, and mount point name, are
in theory both handled now. This was also to fix an osx issue #164 despite the
fact that technically I do not support osx beyond fixing errors, but since in this
case the issue was a long standing one, I fixed it for everything.
4. Big fix, I'd completely left undone proper unix type error number returns in
inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi
returns integer success/error numbers as expected.
5. OSX xml based version info broke, of course, naturally it would, so I added in
an osx fallback where if no distro version detected, use fallback unix method, which
is what all the other unices use.
6. Along with space in source name, fixed mapped handling a bit more too for
partitions.
6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure
how I'd missed those for so long.
7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a,
sigh, human readable default format, in M, so to handle this for all bsds, I had
to make a dynamic column detection for avm and fre, and use those after, and also
i had to add in a M detection, if found, *1024 and strip out M, sigh.
8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks
does not always use the same order in comma separated list, saw user case where
the first item after : was the MB size, not the second. Made detection dynamic.
9. Due to Android case, found types where no cpu speed data was found, no max speed
at least, which tripped an error due to null data for ARM, this is now handled,
now cpu speed min/max read permissions in /sys are checked first before trying to
read, and default failures are better handled.
10. On man page, added in clarification of the moving of Memory: item from Info:
line to ram Memory: line, explaining when it appears where. I do not removing the
item from -I, I may revert that change, I find it non-intuitive to move that
around.
Enhancements:
1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this
closes issues #166 #165 #162
2. Improved documentation a bit to avoid ambiguity re how to get colors in output.
That handles issue #161, thanks fugo for the nudge to improve the documentation.
3. First inxi on Android tests, using termux, which has a debian based apt
type installer, got inxi running on at least two devices, including pixel2, but
discovered that apparently as of android 5, /sys is now locked up in terms of
wildcard reads, but further analysis is required, but as of now, inxi works in
termux, but fails to get any Device data for A, G, or N. Thus it also fails to match
IF to Device, so none of the IP data shows up. The latter will probably be fixed
since Android has ip and ifconfig already, or termux does, but so far I found no
way to get device data for ARM in Android 5.x and greater (checked on
android 7 and 9 in real phones).
4. More disk vendors!! thanks linuxlite / linux hardware database for offering an
apparently never ending list of obscure and not so obscure disk vendors and
products.
5. While I was unable to get confirmation or documentation on file names for
tce repo files, I guessed that localmirrors would be used, but this may be
any random text file in /opt at all, no extensions, I'd have to test to confirm
or deny possible values.
6. To handle more complex debugger failures, added --debug-no-proc,
--debug-no-exit, to skip or enable completion where proc or sys debugger is hanging.
Changes:
1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful
and reliable than I'd first expected when I made the feature, the -xxx was more
an indication of my lack of trust in the method and source, but so far it seems
pretty good, so I bumped it up to an -x option. Note that also, it's quite useful
to know the vendor of, say, your network or graphics card, not just the actual
device internal data, which is all inxi has ever shown previously.
2. Small change, if no partition type data is found, dev, remote, mapped, default
now says 'source:' instead of 'dev:' which makes more sense. Note that df calls
that column 'source', so I decided to go with their language for the default not
found case. Also changed mapped to say mapped. This was part of a bit of a
refactor of the partition type logic, enhanced by adding mapped to existing types,
and moved the entire type detection block into the main data generator, and out
of the data line constructor.
Optimizations:
1. Tested, and dumped, List::Util first() as a possible way to speed up grep
searches of arrays, where the goal is just to see if something is in an array. My
expectation was that first(), returning the first found instance of the search term,
would of course be faster since it will always exit the search loop was met with
the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin.
I tested this fairly carefully, and used NYTProf optimizer tool and the results were
totally consistent, first() was always much slower than grep(), no matter what size
the array is. I assume this means the core C programming that makes grep is simply
much better than the File::Util module programming that makes first(). Removed
first() and now know that nothing will be faster than grep so no need to look there
for speed improvements.
The moral of the story: just because something should in theory be faster, does
sadly not mean it will be faster, for there are bigger things at work, skill of
the programmers who made the logic, how perl handles external vs internal tools,
and so on. As an aside, this forms a fairly consistent pattern where I've found
Perl by itself to be faster than modules in many cases, that is, it's faster to
write the code out than to use a module in many cases that I have tested, so I
will always test such ideas and dump every one that is in fact slower than native
Perl builtins.
2018-10-14 23:16:06 +00:00
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.I https://smxi.org/docs/inxi.htm
|
|
|
|
|
\fR \- The main docs for inxi. See
|
A small point release, mainly to get some bug fixes, and a few minor issues, and
some ongoing updates to various matching rule features like CPU, Disk Vendors,
etc.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. mrmazda, for continuing to poke around and finding oddities on occasion.
2. The various packagers, for continuing to package inxi.
3. Nothing else really comes to mind, so I'm thankful that no real issues popped
up, and the ongoing attempt to stabilize and clean up the several year
aggressive development cycle of code is proceeding quite well.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. I'm currently getting no data samples from new server type CPU systems,
Nvidia Grace, Ampere, both ARM V2 based. The ARM cpu arch logic hasn't been
updated in many years since I have gotten no meaningful data, currently
Raspberry Pi 4 is the latest ARM generation I've seen data for, and no ARM
server type for many years. So support there is really not happening, and won't
be until I start getting real datasets on those server systems.
Nvidia uses Neoverse V2 ARM core, but I have no information on that yet. Also
nothing from the Amazon CPU, new Marvell datacenter type CPUs. But that's not
surprising.Also, nothing from the N1 (2019) or V1 Neoverse (2021) ARM CPU family
even though those have now been out a while.
A lot of the advanced CPU data should 'just work' because of the huge CPU
refactor done recently, but some of the more advanced data, particularly
cpu_arch type data, isn't going to be available until I get real data sets so I
can see what's going on. No idea how CPUID might work for ARM cpus, for example.
Objectively many of these datacenter/machine learning focused CPUs will never
see a system inxi will run on, though most I suspect will be running GNU/Linux
in some form, so inxi can in theory run on them, but those people all know what
their systems are doing, so the need isn't particularly pressing of course.
With this said, I did used to have more access to cutting edge server stuff, but
that has largely dried up, particularly ARM based chips.
--------------------------------------------------------------------------------
BUGS:
1. Found while resolving Fix 2, it turns out > 1 X Screens would not have shown
correctly due to failing to pass $j row counter by reference. This bug was
introduced when the big Monitor updates were done, since you almost never see
> 1 X Screens now, I never saw it until testing something for another reason.
This led to > 1 Screen showing on the same line as the last monitor of the
previous Screen.
See also Fixes 2, 3, 4, and Code 1, 2, 3.
--------------------------------------------------------------------------------
FIXES:
1. Changed Intel Saphire Rapids release data from 2021+ (what Intel had
initially announced) to 2023+ (the actual release date). Not my fault!! They
were too optimistic, inxi merely repeated their claims.
2. While trying to figure out extra Screen showing up, found a series of subtle
issues with how X Screens are handled. Added in more robust test for if Screen
ID has been added by xdpyinfo_data, and other weird corner cases that might
cause strange results in Display Screen-x.
Created check_screen() to allow for more granular and debugable testing.
This forum post helped focus attention on this issue:
https://forum.endeavouros.com/t/\
my-second-screen-is-not-working-after-installing-nvidia/33388
3. %monitors was not correctly assigned in xrandr screen fallback.
4. Set number of Screens found if no xdpyinfo or if xrandr found > xdpyinfo
number of screens.
5. Added Zhaoxin match to Centaur match, might show up on cpu string.
6. OpenBSD's package manager was listed as pkg_info, but it's slightly more
accurate to call it pkg_add. As far as I understand it, OpenBSD doesn't really
have a 'package manager' per se, it has a suite of tools to manage packages.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added some Zhaoxin/Centaur IDs, unlikely to show up, but you never know.
2. Added m68k to X display driver list. This was just added to kernel as a full
drm driver! Very legacy, but has users in vm, qemu, etc.
3. More disk vendors! I skipped updating this last time because, well,
collecting the data is really boring, and slightly tedious, and really serves to
simply remind that this is not the way towards a better world. Or are cheap SSDs
the true path after all? I doubt it, but you never know.
4. New AMD, Nvidia gpu ids.
5. New Intel Cpu Microarch IDs.
--------------------------------------------------------------------------------
CHANGES:
1. No changes to speak of, so I won't.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Various ongoing updates to inxi-perl/docs. These are very slowly being pulled
into a more useful form. Emphasis on slowly.
--------------------------------------------------------------------------------
CODE:
1. In Graphics::xdpyinfo_data() and Graphics::xrandr_data() got rid of extra
step, now just assign hash reference directly to push anonymous hash reference
into array. Had used intermidiate variable assignement of hash ref, but that is
pointless.
2. Added $fake{'xdpyinfo'}, hoping to get some debugger data to test weird
extra 'Screen' seen with Endeavor user (see Fix 2, 3, Bug 1).
3. Also, instead of using \%monitors, which creates a reference to the last
value of %monitors, used the correct and safer {%monitors}, which creates an
anonymous reference of the value %monitors had at that moment. This is a subtle
Perl error which is easy to make in cases where the hash or array reference is
almsot never > 1 instance, such as > 1 X Screens.
This should at least help resolve the repeated 'monitors' rows in the output
in Fixes 2, 3, 4.
4. Added 'source' to $graphics{'screens'} to log where each detected screen came
from, xdpyinfo or xrandr.
2022-12-11 00:04:04 +00:00
|
|
|
\fIinxi\-perl/docs\fR for more technical docs.
|
|
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
.I https://fosstodon.org/@smxi
|
|
|
|
|
\fR \- Follow @smxi on Mastodon!
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.SH AUTHOR AND CONTRIBUTORS TO CODE
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2012-09-15 09:18:08 +00:00
|
|
|
.B inxi
|
2018-04-06 22:52:08 +00:00
|
|
|
is a fork of \fBlocsmif\fR's very clever \fBinfobash\fR script.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
|
|
|
|
Original infobash author and copyright holder:
|
2021-08-25 03:39:33 +00:00
|
|
|
Copyright (C) 2005\-2007 Michiel de Boer aka locsmif
|
2012-09-15 09:18:08 +00:00
|
|
|
|
A small point release, various smaller items, ongoing updates to matching table
features, bug fixes, but nothing major.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. Thanks Umio-Yasuno in github issue #281 for actually being proactive and
finding some Intel/AMD gpu device id lists. I wish more issues would be like
that.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. DEBUG: --debug-arg and --debug-arg-use must use the full format:
--debug-arg="-GS", or else the command line eats the args, even if in quotes.
The error handlers will then complain about no data supplied, and it will exit.
--------------------------------------------------------------------------------
BUGS:
1. GRAPHICS: An accidental 'and' instead of 'or' test (see Code 1) led to
systems without gpu or dri graphics drivers not showing their xorg driver even
when present. This was due to a mistake, and also due to how Perl handles || and
&& in sequence, which made this bug not show up until I tested on a system with
xorg graphics driver, but without dri or gpu drivers. Virtually no modern
hardware or operating systems would trip this condition, but older hardware and
operating systems, which may not have gpu or dri drivers, might. And did, in my
case. This is by the way why I try to test on old hardware at least now and
then.
--------------------------------------------------------------------------------
FIXES:
1. CODE: A poorly done attempt at optimization would have broken case
insensitive pre-compiled regex with $pattern = qr/../ because you can't add
/$pattern/i to precompiled pattern, but qr/.../i support only added perl 5.014.
This should impact almost nobody, but it is/was a glitch. Basically qr/../ can
only be used when no /i type modifier is required if supporting Perl less than
5.014.
See inxi-perl/docs/optimization.txt section REGEX for more on this.
Note that Perl already compares the values in the variable each iteration via a
simple equality test, so the only real gain from using qr// is not having to do
that equality test each iteration of a loop.
2. OUTPUT: Fixed a few small inner key name failures to use '-' instead of ' '
to separate key terms:
3. REPOS: Called urpm urpmq, which is the query tool, not the actual type.
4. GRAPHICS: Fixed some gpu_id.pl matching rules. Thanks Umio-Yasuno in github
issue #281 for noticing that some of the matching rules were either wrong or not
loose enough.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. OPTIONS: Long time oversight, no option to test or do one time change of key:
value separator string ':'. This goes along with existing config option
SEP2_CONSOLE. Added --separator/--sep {character}.
1b. OPTIONS: Added synonym for --output: --export, and for --output-file:
--export-file.
2a. GRAPHICS: New Intel gpu data source, from intel, finally. This let us add a
lot more gpu ids. Thanks Umio-Yasuno in github issue #281 for finding these.
2b. GRAPHICS: New AMD data source, from github. This let me fill in some more,
albeit not as accurately as previous sources, but added more so fine. Thanks
Umio-Yasuno in github issue #281 for finding these.
3. CONFIG: In a first, took a feature from acxi, --config, and imported it into
inxi! This shows active current configuration, by file.
4. CPU: updated, fine tuned amd cpu microarch ids.
5. DISKS: More disk vendors added. Not as many as usual, I think the high tech
sanctions against China may be slowing the rate of new Chinese SSD/USB vendors.
But still some new ones, as always. Not many new IDs for existing ones though,
that is noteworthy. A few new data sources to help pinpoint vendor names found
too, though those won't in general impact users, but can be used to determine if
a string is in fact a company name.
--------------------------------------------------------------------------------
CHANGES:
1. OUTPUT: Fix 2, -t 'started by:' key name changed to: started-by:
-G 'direct render:' changed to 'direct-render:'.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. MAN: there were a few <...> instead of [...] for required option arguments.
Fixed those.
1b. MAN: also added --debug-id [string] since that is in general useful info.
1c. MAN: Added qualifiers about when xwayland: and compositor: items appear for
default -Ga output.
1d. MAN: Typo in config path in man page, .conf/ should be .config/.
1e. MAN: for --output json/xml, added pointer to doc page on smxi.org, people
being unable to grasp the output is getting tiresome.
1f. MAN: Added synonym for --output, --export.
2a. SMXI.ORG DOCS: added --output json/xml documentation page:
https://smxi.org/docs/inxi-json-xml-output.htm - this is also linked to from the
github wiki page, though of course nobody is going to read it, as well as from
a few pages in smxi.org.
2b. Updated inxi-man,options,changelog.htm files.
3. CHANGELOG: Changed to use same format as acxi.changelog, leading topic id's
in upper case, makes it easier to scan read and organize.
4a. DOCS: docs/inxi-cpu.txt - cleaned up, re-arranged a bit, added cpuid data
explanation, and updated header on inxi-perl/data/cpu/microarch to better
explain the way amd does ext fam / ext model, which are not the same,
bizarrrely, very confusing.
4b. DOCS: New: docs/inxi-disks.txt. Split out from inxi-resources.txt, part of
the ongoing to documentation modularization, slowly splitting out sub topics
from inxi-data.txt and inxi-resources.txt. Note this is in general only done
when I'm working on that specific feature. But slowly, surely.
--------------------------------------------------------------------------------
CODE:
1. GRAPHICS: Test when no gpu drivers and no dri drivers but x drivers never
showed x driver. Was supposed to be all || for tests:
if (@$gpu_drivers || $graphics{'dri-drivers'} && @$x_drivers){
https://perldoc.perl.org/perlop. I believe this led to test 1 being false, test
2 being false, and since that left tests 2 and 3 needing to be true for the &&
logical and to be true. Since only one of the two was true, the last bit was
seen as false.
2. GRAPHICS: Connected with 1, noticed that for some weird reason, I'd decided
to assign the array ref for drivers like this:
@$x_drivers = (a, b, c);
when it was supposed to be:
$x_drivers = [a,b,c];
This did not cause any issues, since they mean the same thing, but it was silly
to write it that way.
3a. DEBUG: Added --debug-arg-use which allows testers to run a specific argument
combination that may be causing issues.
3b. DEBUG: Also added more validation, to make sure arg for --debug-arg /
--debug-arg-use start with - or -- followed by a letter.
4. START: Removed this code block from set_konvi_data. I had left this in place
for a release or two to make sure no need for it was found, but it will never be
used since it never worked in the first place.
# my $config_cmd = '';
# there's no current kde 5 konvi config tool that we're aware of. Correct if changes.
# This part may never have worked, but I don't have legacy data to determine.
# The idea was to get inxi.conf files from konvi data stores, but that was never right.
# if (main::check_program('kde4-config')){
# $config_cmd = 'kde4-config --path data';
# }
# kde5-coinfig never existed, was replaced by $XDG_DATA_HOME in KDE
# elsif (main::check_program('kde-config')){
# $config_cmd = 'kde-config --path data';
# }
# elsif (main::check_program('qtpaths')){
# $config_cmd = 'qtpaths --paths GenericDataLocation';
# }
# The section below is on request of Argonel from the Konversation developer team:
# it sources config files like $HOME/.kde/share/apps/konversation/scripts/inxi.conf
# if ($config_cmd){
# my @data = main::grabber("$config_cmd 2>/dev/null",':');
# Configs::set(\@data) if @data;
# main::log_data('dump',"kde config \@data",\@data) if $b_log;
# }
5. OPTIONS: in OptionsHandler::post_process(), reorganized the various run and
exit triggers, help, configs, recommends, version, etc. All on top now.
2023-02-08 01:59:56 +00:00
|
|
|
inxi version: Copyright (C) 2008\-2023 Harald Hope
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
This man page was originally created by Gordon Spencer (aka aus9) and is
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
maintained by Harald Hope (aka h2 or TechAdmin).
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
Initial CPU logic, konversation version logic, occasional maintenance fixes,
|
|
|
|
|
and the initial xiin.py tool for /sys parsing (obsolete, but still very much
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
appreciated for all the valuable debugger data it helped generate):
|
|
|
|
|
Scott Rogers
|
2016-12-21 03:57:41 +00:00
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
Further fixes (listed as known):
|
2016-12-21 03:57:41 +00:00
|
|
|
|
|
|
|
|
Horst Tritremmel <hjt at sidux.com>
|
2012-09-15 09:18:08 +00:00
|
|
|
|
2018-04-04 06:41:06 +00:00
|
|
|
Steven Barrett (aka: damentz) \- USB audio patch; swap percent used patch.
|
2016-12-21 03:57:41 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Jarett.Stevens \- \fBdmidecode \-M\fR patch for older systems with no
|
|
|
|
|
\fB/sys\fR.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
.SH SPECIAL THANKS TO THE FOLLOWING
|
|
|
|
|
|
Huge refactor of CPU physical/core/cache logic. That was some very old logic
with a lot of hacks and patches, but it had never been actually rewritten to
take advantage of Perl's far more powerful and robust data structures and logic.
This caused a continuous stream of error cases in subtle ways, or not so subtle,
and fixes were just changing how the errors manifested.
Tnanks very much to linuxquestions.org Slackware forum people for massive help,
and also to linux.org forum members for ongoing help and data and debugging.
Note Changes 5, change of default widths in display to 80 columns, and out (aka,
console, or ssh into remote system), 100. You can still use other widths if you
like something wider using the configuration options shown. Also upped max
columns wrapping line starters to own rows to 110 columns from 90, again the
idea being to make output more readable to other users when posted in public.
I've been thinking of this change for a long time, but was hoping -y would
register with users, but it hasn't gained enough traction, so the result is way
too many super hard to read issue reports, forum posts, linux kernel issues,
etc, it's honestly gotten sort of embarrassing because they make it look like
inxi has bad output. Sidescrolling code blocks in forums in particular are
absurdly hard to read and scan rapidly for data.
Going along with the width and indentation changes, for most main row types, if
they wrap to a second row, they are further indented 2 column2, to make it
easier to see what they belong to. The two levels of indentation contain more
useful visual cues as to what belongs to what.
There was a temptation to release this as either 3.4.00 or 4.0.00 but in the
end, I decided to follow the numbering rules, and to just roll it to 3.3.10
since there aren't really any primary new features even though CPU was basically
rewritten in large part, and big parts of inxi were also changed, upgraded, and
enhanced. But no truly new features, just some display control items like -Y,
--indent, --indents.
I hope this refactor meets its primary goals, and that the new defaults for
display help resolve public posting issues which have grown increasingly
annoying for anyone trying to read those pasted in too long outputs.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Android seems to have CPU cache data, but does not show any 'size' item. But
it does have the other data for each cache type internally, which is odd.
2. In some instances, the parent key:value pairs with '' as value, those are
parents of children key:value pairs, are left hanging at end of line, with the
children on the following line. This can look awkward, but in other cases,
actually looks very good, it depends if it's at the start or end of the line.
I won't say this is not correctable, but it would be very difficult, and outside
the scope of this release, but that is something that I may look at for a future
release now that the output generator logic was reworked slightly for Change 5b.
It's tricky though, because in cases where it's the first item on the line, you
want that behavior, but when it's last, you don't. But this may be worth
revisiting in the future.
3. In some cases, -Y + -y1 may lead to the start of the block scrolling off the
top of the visible screen. This isn't really correctable, so if that's an issue
for you, just don't use -y1 with -Y and all the output will wrap nicely.
4. There is an unaccountable ~10-20ms delay reading cpufreq/scaling_cur_freq,
per thread/core, which really adds up on high thread count CPUs. There is a
workaround in inxi to use cpufreq_cur_freq if it is readable, ie, if you are
root or use sudo, but to fallback to scaling_cur_freq if can't read cpuinfo_...
This is a drag, and really looks like a kernel bug, or a frequency driver bug.
--------------------------------------------------------------------------------
BUGS:
1. 3.3.09 and 3.3.10 CPU bug fixes:
* Failed to filter out certain virtual machine CPU core speeds, and showed more
speeds than the instance actually has. Noticed this with KVM running on Xeon
CPUs.
* For many cases, L2 cache, particularly for Intel, was completely wrong, it was
showing L3 caches, or L3+L2. Failed to handle cases where L2 cache belongs to
more than 1 core, except for using a crude hack for AMD Bulldozer microarch.
Older Intel Core 4 core CPUs would sometimes be 1 L2 per die, and the 4 cores
were actually 2 core duo cpu dies, with one L2 cache per die.
* Shows wrong core count for complex core complexes like those found in Intel
Alder Lake, now shows correct count of actual cores, regardless of the MT or ST
state of each core.
* Showed invalid L3 cache values in some legacy cpus that had no L3 cache, that
is due to a bug in the dmidecode data itself. Solution is to never use dmidecode
cache data if any other valid L1, L2, or L3 cache data found for Linux, and to
only use dmidecode data for bsds if no L1, or L2, or L3 data found. Or if forced
with --dmidecode.
2. An unfortunately long standing bug found and fixed, thanks slackware users!
cp_cpu_arch was, and has been for a while, failing to convert hex stepping to
decimal, or test if the string it gets is even a possible hex value, this
resulted in all Intel CPUs with stepping > 9 failing to ID correctly for cpu
arch.
3. In a related bug, hex to decimal tool used to create --admin hex/decimal
output for family/model/stepping was also not testing if the string was an
actual valid hex number. Case in particular, power pc with revision field
contained a long string, which was of course not a valid hex number, and that
tripped a Perl error when it was asked to convert a non hex string to decimal.
4. Long standing bug found while doing Change 5: inxi actually never applied
separate in/out of dispay to widths because using a legacy boolean that was not
updated, so it was always using out of display widths.
--------------------------------------------------------------------------------
FIXES:
1. Incorrectly calling PowerPC 'revision' 'stepping' for -Ca, that is now stored
as $cpu{'revision'} to avoid mixing up the logics there. For PowerPC shows as
rev: [string].
2. Microarch:
* AMD family 15, model 2 as bulldozer, actually piledriver.
* AMD family 17, model 18, was supposed to be zen/zen+, since I can't tell those
apart, seen stepping 1 is zen+, but had incorrect match.
* Intel family 6, model 25, stepping 2 as nehalem, should have been westmere.
* Changed Penryn to Core Penryn, intel family 6, model 17
* misc other micro arch fine tunings.
3. Code fix 8, switched to global %risc for arm, mips, ppc, riscv, sparc. This
corrects many sloppy handlers, and makes all risc processing the same, and calls
device tree readers for all risc systems, not just arm or arm and mips.
4. In cases where bogomips were 0 due to false values in risc results, show N/A.
5. Removed all attempts to guess at what /proc/cpuinfo cache size: refers to,
it can literally be anything, a per core L1, a per core or cpu L2, or an L3.
So applying any math to it is just a random guess at that point. If any L1,2,3
cache data is found, don't use the cache: value at all, but that will only be
present if no /sys data was found anyway, and if cpuinfo had no specific cache
type fields, only generic cache.
6. Added failsafe tests for stepping and model id before doing conversion to
hex. Make sure integer!
7. Added L1 D cache, was only using I cache for BSDs. Output will show total for
L1 A + L1 D. No idea why I didn't use L1 D, makes little sense, but that's how
it goes.
8. Made bogomips tests more granular, now only rejects low sub 50 bogomips
values if %risc cpu type. Legacy ancient cpus like 486 could and did have
bogomip counts below 50.
https://tldp.org/HOWTO/BogoMips/bogo-list.html
9. See Enhancement 12 as well. If OpenBSD, which has no per core data or
physical cpu data, is running on MT capable cpu, but for security OpenBSD has
disabled MT, will now force MT to be not shown via the hw.smt value. This
removes a small glitch that would have bothered OpenBSD users who know that
OpenBSD has disabled MT for security purposes.
10. Changed BSD hack to use L2 cache totals to deduce > 1 physical cpus, that
was flat out dumb, since we can just use dmidecode type 4 to iterate physical
cpu counts and skip the pointless logic. Thus, if dmidecode, and if > 1
dmidecode type 4 found, and if physical cpu counts equal 1, then replace the
found counts with the dmidecode physical cpu counts.
11. Corrected bad assumption that threads would always be 2 per core for MT
tests. Still no way to reliably determine threads per core for non x86 cpus like
powerpc however, but those are very fringe and should rarely be an issue since
that data is only missing on very old linux now I think.
12. Fixed 'parameters:' going to its own line with -Sa, that wasn't supposed to.
-S is two lines, the kernel / host stuff, and the desktop/console/distro stuff.
13. Fixed case when key: value first word plus other parts of line longer than
max width, failed to wrap as expected.
14. Added start/end ' and " start / end \s to main filters.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. CPU: most Linux will now show L1 and L3 cache with -Cx without needing
sudo/root, and it will be more accurate than ever before.
2. CPU: shows per CPU L1/L2/L3 totals, and shows actual full system physical
processor count * L1/L2/L3 total in parentheses, like: L2: 1.5 MiB (3 MiB).
3. CPU: A long standing annoyance, previously for main CPU 'Speed:' item, showed
the fastest core speed found, now shows avg: [speed] and with -Cx, shows the
'high:' as well if > 1 cores, and if 1 or more cores have a higher speed than
the other(s).
4. CPU: Handles advanced cases of new architectures, like Alder Lake with
Performance and Efficiency cores, future Zen, and existing ARM CPUs with 2 or
more different core sets, with different max/min frequencies. Previously a hack
was used to handle only ARM CPUs with this type of architecture. Will show
correct CPU core counts, which previous inxi versions would fail to do for Alder
Lake type scenarios of 8 single threaded CPUs and 4-8 multithreaded )MT)
perforance cores.
This should also in theory show different the different min/max speeds if they
were detected. Those did not seem to be set correctly in Alder Lake sample data
I saw however, P and E cores were set to the same min/max speeds.
5. Added CPU types MST (Multi+Single Thread), AMP (Asymmetric Multi Processing),
and AMCP (Asymmetrical Multi Core Processor). This will be applied to any CPU
that has this type of complex topology that has been dynamically detected, like
Alder Lake or different core count or min/max speed RISC CPUs.
6. CPU: shows with -Ca for cases where different L1/L2/L3 caches found per
physical CPU, as with Alder Lake, but also many other variants that were poorly
or not at all handled before, how many of each cache type (L1 Data, instruction)
were found, otherwise will show how many of each cache were found.
7. CPU: shows with -Ca in Topology: report, for cases like Alder Lake with
different core types in one physical CPU (type: MST AMCP), the number that are
single threaded (st) and number that are multi-threaded (mt).
8. Basic support for rsyc-v systems, going along with code fix 8, fix 3, now
it's easy to add this type of support.
9. Added shortcut options for --filter-label (--zl), --filter-uuid (--zu), and
andded new filter option, --filter-vulnerabilities (--zv). The latter is added
by request, a decent idea to have option to not show cpu vulnerabilities.
10. Going with fix 7, switched to a sort of pseudo L1 d/i with desc report for
any BSD with L1 I/D cache found, or elbrus cache0 (icache) / cache1 (d cache).
Elbrus should hopefully be handled by the /sys tool. Guesses on the L1 are ok,
since those are almost always per core, so it's fine. Didn't expect to enhance
any BSD cpu data this time around, but there you go!! If they have the data,
then it will be used. Not going to go overboard though in that, quite useless
overall since usually can't see how many CPUs are present, at least not usually.
11. For -Ca, full CPU topology report if any complex topogy is detected,
otherwise shows the same basic Info: 2x 6-core or Info: dual core as before, no
point in wasting a line for something with no more data than the short string.
Complex types include MT CPUs since they will have different thread counts etc,
and will have 2 or more threads per core, which will also be listed.
12. If smt status is defined (0/1), shows smt: enabled|disabled in Topology
section, can be useful for systems with disabled MT, but supporting it. If no
topology data found (OpenBSD for example), for -C shows 'smt: disabled' after
'type:' section, and enabled if -Cxxx (since MT really already tells you that).
13. For -Ca Speed: report, added 'governor:' item, if found. Can show 1 or more
active governors.
14. Output height (in lines) control: -Y [-2|-1|0|1-xxx]]. This lets you break
up any of the output into whatever number of lines you want. Also useful out of
DISPLAY for reading -h options menu items etc.
It came tp my attention that the long standing shift+pgup/pgdown (aka
'softscrollback) behavior had stopped working, and in fact has been removed from
the current Linux kernel, at least until it is rewritten to be more clean and
understandable. Read more about it in these kernel post/commit messages:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://lwn.net/ml/linux-kernel/CAHk-=whe4ZdTdCebneWqC4gSQZwsVJ5-Emg0BucOGCwPhOAJpw@mail.gmail.com/
Options for -Y are:
* -Y 0 or -Y: Set maximum block height to terminal line height.
* -Y [1-xxx]: Set maximum block line height to given integer.
* -Y -1: Print out one primary data block item at a time, with -F for example.
* -Y -2: Restore default unlimited height if LINES_MAX configuration item used.
15. And finally, more disk vendors/vendor ids. As usual. As expected.
--------------------------------------------------------------------------------
CHANGES:
1. If /sys or /proc/cpuinfo speed data available:
* For -b CPU item:
speed: [speed MHz] min/max: [min]/[max] MHz
becomes:
speed (MHz): avg: [speed] min/max: [min]/[max]
* For -C, Speed item
Speed: [speed MHz] min/max: [min]/[max] MHz Cores (MHz): ...
becomes:
Speed (MHz): avg: [speed] min/max: [min]/[max] cores: ...
* For short form, shows speed/min/max but uses average speed if available.
For -b and -C, only shows one MHz in Speed line starter, which slightly shortens
the line even with the added 'avg:' item since 3 MHz are replaced with 1.
2. Going with change 1, now the 'avg:' item shows not the fastest cpu speed
found, which was the case before, but shows an average of all cpu speeds found.
Showing the fastest made some sense back in the days of single core, or even
dual core CPUs, but makes little sense today with many core/threaded cpus.
With -x, it will show the high: [speed] item as well, after 'avg:'.
3. By suggestion, wrapped first Type item in Vulnerabilities to its own line,
that's a verbose --admin option after all, no need to save lines!
4. Going along with Fix 5, give up on trying to pretend we can guess at L2
cache, now if only 'cache' data was available from cpuinfo, will just say:
cache: [cache size]
note: check
and call it a day.
5a. Change default width to 80 columns, in and out of display. Too many users
are posting horribly wrapping inxi output in forums, issue trackers, etc, and it
frankly makes inxi look really bad, creates awful side scrolling code boxes,
etc. So now default widths in and out of console are 80 (since often data is
generated in SSH or out of X/Wayland) for issues.
This essentially makes -y 80/-y the default width. This is what I've been using
for a few years now, and after seeing far too many side scrolling or badly
wrapping inxi outputs online, I think it's probably time to just force 80 column
widths as default and call it a day.
You can change these new defaults using configuration options (these are the
previous options, though due to a bug, COLS_MAX_CONSOLE was never being used):
COLS_MAX_CONSOLE=115 # in display, terminal client max width
COLS_MAX_IRC=100
COLS_MAX_NO_DISPLAY=130 # not in display, no X/Wayland running
5b. Changed output wrapped indent to 1 column from 2, and make second and
greater rows of a line indent +1 to make it more clear that it is a child row of
its parent row. Note that because no arg short form, -S, and -I are special
types of rows, this behavior is not used, they just print out as usual. This 1
column indent also applies to -y1, making for a little more data per line but
more readable and easy to follow.
6. If > 1 physical cpu detected, no longer uses single/dual/triple/quad core
strings, rather uses: 2x 2-core. Also uses lower case -core, not -Core.
7. Only show die counts for CPU (on rare occasions > 1 found) with -xx. Not
particularly important bit of data afterall.
8. Make L1, L3 cache data show with -Cx, not -Cxx, now that it's working well.
9. Removed CPU die for -Cxx, that's only going to show with -Ca now.
10. If -Ca, and if certain complexity conditions are met, shows a separate
Topology line rather than the Info: 6-core type item. For -b, short, -Cx, -Cxxx
shows the Info: topology short form.
11. Bogomips always shows before flags data, whether -f or just -Cx trips flag
output.
12. Flags/Features now shows in the same place, under Speeds: always, whether
-Cx shortlist, or -Cf full list. Makes more sense that way, and code is much
cleaner too.
13. Bogomips, being essentially bogus units of speed for cpu, are moved into
Speed: report.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Updated man/help for new CPU extra data options and output changes.
2. Cleaned up and added sample outputs for man CPU items.
3. Now that doas is getting into Linux distros, removed all mentions of doas as
a BSD option, and made it a general doas/sudo item. Glad to see doas making it
into linux distros, it's a good tool, much easier to configure and use than
sudo. Good job OpenBSD guys. Note that inxi already has had full doas support
for a while now, but this finalizes it, and makes it fully agnostic. Internally
doas is actually preferred over sudo, by the way.
4. Added documention items for INDENT (--indent), INDENT_MIN (--inident-min).
5. Re-ordered help menu and man page, created new Filters and Output Controls
sections to make stuff easier to find. In man page, also added on top a list of
OPTIONS sections to make finding stuff easier.
--------------------------------------------------------------------------------
CODE:
1. Removed legacy /sys cpu functions: cpu_bugs_sys(); get_boost_status();
set_cpu_speeds_sys(). cpu_speeds() is deprecated and now will only be used for
legacy Linux and BSDs if they had any per core speeds found; get_caches() was
only a placeholder for the full featured cpu_sys data source, and was removed;
cpu_speeds() no longer needed, integrated into other logic; cpu_dies_sys()
removed, integrated into other logic.
This logic is now integrated into cpu_data_sys() data generator.
2. Changed the main CpuItems functions to use array/hash references, not passing
full hashes or arrays in most cases now.
3. For machine_data_soc(), switched to CpuItem::cpuinfo_grabber() which then
sets the global @cpuinfo and %cpuinfo_machine items, which will be used again
in Cpu if cpu data is requested. This gets rid of a full parsing of cpuinfo
just to get the machine data section, and also makes it so cpuinfo in cpu does
not need to worry about the machine data block, which is not related to the
processor blocks anyway, that was always a hack done by the kernel guys to toss
that SOC data somewhere as far as I can tell.
4. New tools:
* either_or() - takes a list, and returns the first defined element of list.
* regex_range() - generate ranges from comma, space, or ranges like 2-29, or any
combination of those, like 3,6,12-29
5. Added --force cpuinfo to bypass all /sys based cpu logic, useful for testing
to see what would have happened using old logic.
6. Added --dbg switches 39, 40, 41, for the new cpu sys data features, also made
more consistent --dbg 8 and --dbg 38 switches.
7. Added sys/cpuinfo pair debugger to support debugging complex sys/cpuinfo
issues.
8. Got rid of $b_arm,$b_mips,$b_ppc,$b_sparc, replaced with global %risc, also
added $risc{'riscv'} type. this makes general risc type feature testing a lot
easier since inxi can either test for %risc defined, or for a specific type of
risc cpu. This is much cleaner, and use $risc{'id'} for print purposes, which
got rid of a lot of tests. Also made all risc tests consistent, some were ARM
only, or arm/mips, but were supposed to be for all risc cpus.
9. Set help menu code to roughly 80 columns width assuming 2 space tab
indentation.
10. Changed all xxx_cleaner subs to clean_xxx, all filter subs to filter_xxx,
and row_defaults() to message().
11. Dumped redundant fallback logic in get_kernel_bits, if first getconf method
fails, use $sys_bits, and call it good, it was repeating the 32/64 bit tests
pointlessly.
12. Cleaned up print_data() to allow for more fine tuned indentation for the new
2 indent levels.
13. Made help menu code more or less wrap to 80 columns, or close. Ongoing to
bring to 80 columns where practical, but never at expense of clarity or logic.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 13 Dec 2021 10:25:49 -0800
2021-12-14 18:35:42 +00:00
|
|
|
The nice people at irc.oftc.net channels #linux\-smokers\-club and #smxi, who
|
|
|
|
|
all really have to be considered to be co\-developers because of their non\-stop
|
|
|
|
|
enthusiasm and willingness to provide real\-time testing and debugging of inxi
|
|
|
|
|
development over the years.
|
|
|
|
|
|
|
|
|
|
LinuxQuestions.org Slackware forum members, for major help with development and
|
|
|
|
|
debugging new or refactored features, particularly the redone CPU logic of
|
|
|
|
|
2021\-12.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Siduction forum members, who have helped get some features working by providing
|
|
|
|
|
a large number of datasets that have revealed possible variations, particularly
|
|
|
|
|
for the RAM \fB\-m\fR option.
|
2016-12-21 03:57:41 +00:00
|
|
|
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
AntiX users and admins, who have helped greatly with testing and debugging,
|
2018-04-06 22:52:08 +00:00
|
|
|
particularly for the 3.0.0 release.
|
2016-12-21 03:57:41 +00:00
|
|
|
|
New version, new man. Bug fixes. BSD fixes.
Bugs fixed:
1. CPU: MT/HT was wrong for old xeon, made mt detection more robust and hopefully
more reliable, removed all explicit b_xeon based tests.
2. fixed /dev/mapper glitch, that make /dev/mapper links fail to get id'ed.
3. openbsd: fixed memory handler; fixed cpu flags, fixed partitions handling.
4. freebsd: fixed similar partition bugs, these were caused by the darwin patch.
5. man page: fixed top synopis syntax, thanks ESR.
6. partitions fs: fixed possible failures with lsblk fs. lsblk: added debuggers
so we can track down this failure in the future.
7. added sshfs filter for disk used output, note, there is a possible syntax for
remote fs that isn't handled: AAA:BBB that is, no :/, only the :. This makes
explicit detection of still unknown remote fs very difficult since : is a legal
nix filename character.
2018-04-19 02:35:49 +00:00
|
|
|
ArcherSeven (Max), Brett Bohnenkamper (aka KittyKatt), and Iotaka, who always
|
|
|
|
|
manage to find the weirdest or most extreme hardware and setups that help make
|
|
|
|
|
inxi much more robust.
|
New inxi, new man, new tarball.
It's here! Perl inxi, first official release. So many changes, really too many
to list.
But here's a few:
1. of course, full rewrite to Perl 5.x. Supports as old as 5.008, as new as current.
2. Better line length nandlers. Fully dynamic, robust, shrinks and expands to fit
either taste or viewport.
3. Long options for all options now, plus of course the short options everyone
is used to.
4. New options: --usb; --slots (pci slot report); --sleep (change cpu sleep time);
and many more. Check --help or man page for details.
5. Vastly improved --recommends, now does per distro package recommends, and shows
only Linux data to Linux systems, and BSD data to BSD systems.
6. Hugely improved debugger as well.
7. Far more accurate output, most output is now in key/value pairs, because:
8. inxi now exports to json and xml! See --output/--output-file for info.
9. Enhancedd repo output, added deb822 type, solus
10. Radically enhanced network data, now shows all IP / IF devices connected to
each nic, not just one, both IP v4 and v6.
11. USB audio and network device actual drivers
12. better handling of compiler data.
13. Basic ARM machine data now, if present to inxi
14. Graphics: per card driver info alongside the original xorg drivers.
15. Better integration of partitions, RAID, unmounted partitions, and HDD data.
16. Better sensors handling of free video driver sensor data, well, not better,
it's now there, along with fan speeds for gpus.
17. RAID is enhanced, and now can show > 1 RAID type on a system, and the RAID
is improved.
18. Much improved disk/partition/memory sizing, inxi now always works internally
with KB units, and changes them on output to the appropriate units.
19. Fully redone man page for all the new options and the long options.
And so much more. Anyway, here it is, the first release.
2018-03-20 10:06:46 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
For the vastly underrated skill of output error/glitch catching, Pete Haddow.
|
|
|
|
|
His patience and focus in going through inxi repeatedly to find errors and
|
|
|
|
|
inconsistencies is much appreciated.
|
|
|
|
|
|
|
|
|
|
For a huge boost to BSD support, Stan Vandiver, who did a lot of testing
|
|
|
|
|
and setup many remote access systems for testing and development.
|
New version, new man. Very new man.
Man features new section, configuration options, which lists the main config options
users would be likely to use.
This should help users who will never check the actual documentation web page
realize that there are many internal configuration options available.
Many edits in man, more to come I suspect.
Bug fixes in inxi:
1. removed a few stray debuggers that were creating debugging output
2. fixed a usb driver bug that would create warning messages from Perl (thanks Manjaro
for finding that one)
New Option:
1. Added: --indent-min - goes with the user configuration option: INDENT_MIN
and allows users to experiment with different indent settings. This is what trips the
auto line wrap of line starters. This may be revisited, and this switch will make it
easier for users to see for themselves which they prefer, what trip point, etc.
This will help determine pre 3.0.0 what the default auto wrap trip point, if any,
will be.
Added more data to debugger tool, more lsblk, which is going to need a lot more data
to solve a new issue with dm/encrypt/lvm, initial $MANPAGE data, to see if anyone
actually ever uses that environmental variable.
Special thanks to Manjaro for being as far as I know the first to package Perl inxi.
2018-03-25 01:14:24 +00:00
|
|
|
|
A small point release, mainly to get some bug fixes, and a few minor issues, and
some ongoing updates to various matching rule features like CPU, Disk Vendors,
etc.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. mrmazda, for continuing to poke around and finding oddities on occasion.
2. The various packagers, for continuing to package inxi.
3. Nothing else really comes to mind, so I'm thankful that no real issues popped
up, and the ongoing attempt to stabilize and clean up the several year
aggressive development cycle of code is proceeding quite well.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. I'm currently getting no data samples from new server type CPU systems,
Nvidia Grace, Ampere, both ARM V2 based. The ARM cpu arch logic hasn't been
updated in many years since I have gotten no meaningful data, currently
Raspberry Pi 4 is the latest ARM generation I've seen data for, and no ARM
server type for many years. So support there is really not happening, and won't
be until I start getting real datasets on those server systems.
Nvidia uses Neoverse V2 ARM core, but I have no information on that yet. Also
nothing from the Amazon CPU, new Marvell datacenter type CPUs. But that's not
surprising.Also, nothing from the N1 (2019) or V1 Neoverse (2021) ARM CPU family
even though those have now been out a while.
A lot of the advanced CPU data should 'just work' because of the huge CPU
refactor done recently, but some of the more advanced data, particularly
cpu_arch type data, isn't going to be available until I get real data sets so I
can see what's going on. No idea how CPUID might work for ARM cpus, for example.
Objectively many of these datacenter/machine learning focused CPUs will never
see a system inxi will run on, though most I suspect will be running GNU/Linux
in some form, so inxi can in theory run on them, but those people all know what
their systems are doing, so the need isn't particularly pressing of course.
With this said, I did used to have more access to cutting edge server stuff, but
that has largely dried up, particularly ARM based chips.
--------------------------------------------------------------------------------
BUGS:
1. Found while resolving Fix 2, it turns out > 1 X Screens would not have shown
correctly due to failing to pass $j row counter by reference. This bug was
introduced when the big Monitor updates were done, since you almost never see
> 1 X Screens now, I never saw it until testing something for another reason.
This led to > 1 Screen showing on the same line as the last monitor of the
previous Screen.
See also Fixes 2, 3, 4, and Code 1, 2, 3.
--------------------------------------------------------------------------------
FIXES:
1. Changed Intel Saphire Rapids release data from 2021+ (what Intel had
initially announced) to 2023+ (the actual release date). Not my fault!! They
were too optimistic, inxi merely repeated their claims.
2. While trying to figure out extra Screen showing up, found a series of subtle
issues with how X Screens are handled. Added in more robust test for if Screen
ID has been added by xdpyinfo_data, and other weird corner cases that might
cause strange results in Display Screen-x.
Created check_screen() to allow for more granular and debugable testing.
This forum post helped focus attention on this issue:
https://forum.endeavouros.com/t/\
my-second-screen-is-not-working-after-installing-nvidia/33388
3. %monitors was not correctly assigned in xrandr screen fallback.
4. Set number of Screens found if no xdpyinfo or if xrandr found > xdpyinfo
number of screens.
5. Added Zhaoxin match to Centaur match, might show up on cpu string.
6. OpenBSD's package manager was listed as pkg_info, but it's slightly more
accurate to call it pkg_add. As far as I understand it, OpenBSD doesn't really
have a 'package manager' per se, it has a suite of tools to manage packages.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Added some Zhaoxin/Centaur IDs, unlikely to show up, but you never know.
2. Added m68k to X display driver list. This was just added to kernel as a full
drm driver! Very legacy, but has users in vm, qemu, etc.
3. More disk vendors! I skipped updating this last time because, well,
collecting the data is really boring, and slightly tedious, and really serves to
simply remind that this is not the way towards a better world. Or are cheap SSDs
the true path after all? I doubt it, but you never know.
4. New AMD, Nvidia gpu ids.
5. New Intel Cpu Microarch IDs.
--------------------------------------------------------------------------------
CHANGES:
1. No changes to speak of, so I won't.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Various ongoing updates to inxi-perl/docs. These are very slowly being pulled
into a more useful form. Emphasis on slowly.
--------------------------------------------------------------------------------
CODE:
1. In Graphics::xdpyinfo_data() and Graphics::xrandr_data() got rid of extra
step, now just assign hash reference directly to push anonymous hash reference
into array. Had used intermidiate variable assignement of hash ref, but that is
pointless.
2. Added $fake{'xdpyinfo'}, hoping to get some debugger data to test weird
extra 'Screen' seen with Endeavor user (see Fix 2, 3, Bug 1).
3. Also, instead of using \%monitors, which creates a reference to the last
value of %monitors, used the correct and safer {%monitors}, which creates an
anonymous reference of the value %monitors had at that moment. This is a subtle
Perl error which is easy to make in cases where the hash or array reference is
almsot never > 1 instance, such as > 1 X Screens.
This should at least help resolve the repeated 'monitors' rows in the output
in Fixes 2, 3, 4.
4. Added 'source' to $graphics{'screens'} to log where each detected screen came
from, xdpyinfo or xrandr.
2022-12-11 00:04:04 +00:00
|
|
|
For testing, bug finding, suggestions, feature requests, MrMazda. He has over
|
|
|
|
|
the years has helped shape inxi into what it is today, in particular but not
|
|
|
|
|
limited to, the Graphics features.
|
|
|
|
|
|
2018-04-06 22:52:08 +00:00
|
|
|
All the inxi package maintainers, distro support people, forum moderators,
|
|
|
|
|
and in particular, sys admins with their particular issues, which almost always
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
help make inxi better, and any others who contribute ideas, suggestions, and
|
|
|
|
|
patches.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
Without a wide range of diverse Linux kernel\-based Free Desktop systems to
|
|
|
|
|
test on, we could never have gotten inxi to be as reliable and solid as it's
|
|
|
|
|
turning out to be.
|
2012-09-15 09:18:08 +00:00
|
|
|
|
Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth
fixes!! What are you waiting for?!!?
A special thanks for significant help, ongoing, leading to a huge boost to BSD
support, Stan Vandiver, who did a lot of BSD testing, and setup many remote
access systems for testing and development of the latest BSD upgrades. If you're
a BSD user, you can thank him for helping to expand BSD support!
Take special note of the code folding fixes in Fix 1, those open up possible
free software code editors that can be used to work with inxi to more than just
Kwrite/Kate, to include scite and geany, nice lightweight code editors. You
can't do real work in inxi without code folding, so getting this finally
resolved was I think worth it.
Also, for the first time ever!! inxi is now using Pledge, well, if
OpenBSD::Pledge module is available, which is currently only in OpenBSD, since
that's the only system that supports Pledge security, except for Serenity, but
inxi doesn't support Serenity. Note that OpenBSD was smart and added
OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop
that might stop a Perl program from implementing it. Nice going OpenBSD guys!
The addition of OpenBSD softraid support for RAID and CRYPTO types highlights
the problem with --raid and --logical, where --raid is really just a subset of
Logical volume management. Note that while the hardware RAID feature only lists
the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the
box, something I'd thought of doing in inxi for a few years, but it's too much
work, but bioctl has done the work, which is impressive. Can't do much without a
lot of debugger data there though, but it's worth being aware of. In this case,
since softraid is the primary device, I opted to call Crypto and RAID types all
RAID, same as with linear zfs.
--------------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic
to be stable across systems and varying syntaxes used. Will wait for FreeBSD to
add drivers to usbconfig -vl. Note that this makes it not possible to correctly
match USB networking devices to their respective IF data, so USB networking IF
will fall back to the undetected IF-ID, which means it was found but not
connected to a specific hardware device.
2. FreeBSD Battery Report: there are non-objective values for Battery state data
in sysctl output, as in minutes remaining, which has no meaning, and percent
charge (percent of what? original design capacity? current actual capacity?). If
data with voltages, design/current capacity in Ah or Wh, is made available,
support will be added. Note that there are 3rd party tools that do supply this
data in a usable format, but they are not in core so no point.
3. BSDs All: have found no way to get physical CPU counts. this will lead to odd
outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual
core counts single CPU, but the data just isn't there as far as I know.
Dragonfly in some cases appears to have that data.
4. BSDs All: so far no way to get live per core cpu speeds using a file or fast
command query. Thought I'd found a way in FreeBSD but that was not the correct
clockrate values, or inconsistently right/wrong, so not using it. Also saw the
same issue with max/min frequencies in FreeBSD so removed that item, it's
better to show nothing than data that is not reliable or actually not even
referring to what it seems to be.
5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in
general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is
simple: to do SOC ARM device data in a meaningful way requires a complete path
based data structure, which the BSDs do not appear to have, at least from what
I've seen so far. See Linux's /sys data structures for examples of what is
required to add or expand inxi SOC device support in inxi. It's hard even with
that type of rich path based data, and without it I won't try.
The bright side is inxi runs perfectly on such devices, no errors, which was
amazing to see, and spoke volumes of the recent work done to extend support for
the BSDs.
6. Perl / inxi, when run as root, shows read error when trying to open a 200 /
--w------- permission /sys uevent file for reading. The test works as expected
as user, but not as root. Perl will try to read it when run as root even though
it has no read permissions, only write. This in reality only manifests on very
old /sys, from Debian Etch kernel 2.26 days.
--------------------------------------------------------------------------------
BUGS:
1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that
leads to failed terminal/console size from tput. Also while trying to resolve
this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for
some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who
knows. Added in non numeric tests of output to handle errors from tput instead.
The bug appears to be what rxvt reports itself as vs what it is actually running
as. This issue isn't present in any other distro I tried, but could just be a
new bug in urxvt, don't know.
2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo,
that exposed some bugs internally in inxi Elbrus handling, I was using integer
values instead of hex for model IDs in the Elbrus logic, which would fail after
model 9.
3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and
had to be fully redone because of the need to detect in a reliable way the
current state of USB drives. This logic now is much more robust and reliable,
and no longer relies on using 'uniq' values per line, which would fail in all
kinds of situations.
4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during
the USB data refactor testing process.
5. BSDs: in some cases, wrong memory used values were being generated, this
should be largely corrected now. Also pulled the weird NetBSD use of
/proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which
after the used bug fixes, is more reliable for BSDs.
6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came
across some systems with an actual stepping: 0, which are not common.
7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in
some cases. Due to no MT detection possible for FreeBSD currently, these totals
will still be wrong, but now it says note; check to let users know.
8. dmidecode: some cases were getting the wrong failure error message, this bug
became exposed due to OpenBSD locking /dev/mem even to root, which then failed
to show the expected message. This was a bug, and is now corrected.
9. FreeBSD: partition swap size didn't show in at least some cases, that's
corrected.
10. Linux Partitions: partitions would let doubled swap items through in several
cases, and also failed to create in rare cases matches for hidden partition
mapped id's. Finally tracked down the actual cause, when moving the partition
filters I'd forgotten to add swap into the filter list, oops. But now it will
catch duplicates in several different ways, so that's fine.
11. Unmounted: Failed to properly handle detecting RAID components in the case
of lvm, mdraid, it was only working for zfs. This was an accident, and should
now be corrected.
--------------------------------------------------------------------------------
FIXES:
1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug
in scintilla/scite geany code editors with folding, basically if you commented
out logic, without using a space or other marker after the comment #, folding
would break in weird ways. Obviously the core scintilla engine should IGNORE the
darned # commented out lines, but it doesn't, which is a real bug. But not in
inxi.
This was however worth working around, because without folding, you can't work
on or learn how inxi works, and the only editor I know of in the free software
eco-system that can handle folding reasonably accurately was until now
Kwrite/Kate code editors, and those have some real, long standing, weaknesses,
and bugs around folding that have never been resolved, and yes, did notify them
about them, and no, they remain unfixed after years, or they were fixed briefly,
then broke again.
So it was important to expand the base of possible code editors to more than
just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright
side, geany/scite folding / unfolding is FAST, and once the code issues that
triggered folding failures were resolved, very accurate, much better than Kate's
to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been
broken more often than it's worked.
To avoid this issue, it's also important to configure geany/scite to use a space
after the comment when using keyboard shortcuts to comment out lines/blocks.
Same goes for Kate/Kwrite, by the way.
2. Battery: Forgot to add battery-force to -v7, which means you would never see
the battery line in full output if there was no battery present, this is similar
to how raid-forced worked, it was just an oversight which I hadn't noticed until
testing the new BSD battery logic.
3. Indentation: small indentation fixes on Sound Server data. Those are visible
with -y1, that is.
4. OpenBSD PCI: enabled Device matching to PCI networking device, this required
an odd little hack, but seems to be pretty reliable, and allowed me to add
driver to PCI device reports as well. Not sure why driver isn't in pcidump -v
but it probably will be in the future. Note to self: add in support for that so
if they include it in a future release, it will suddenly 'just work', assume
they use the same basic syntax as usbdevs -vv output.
5. BSDs: Added in some null data protections for BSDs, which do not always have
all the data types found in Linux, those would trigger Perl undefined value
errors, which are warnings that inxi failed internally to test for null data in
that, but it's hard to know when to do that when the data is basically always
there in Linux.
6. Debugger: Added test for required Net::FTP module in debugger, had forgotten
to make that test explicit, which led to odd failures.
7. BSDs: nvme detections should be better now. But I have seen no live test
system to confirm the fixes work as expected, plus, at least, OpenBSD swaps
nvme0 to sd0 internally, so I'm not actually sure how that data will even work,
we'll see how that goes.
8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU
stepping, the stepping is in decimal, which is even odder because CPU makers
list their steppings as hex in many if not most cases. In case this is corrected
in the future, if 0x appears before stepping number, will not then try to
convert to hex since it already is.
9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical
CPU in every case I've found, so never multiply value by cores for L3. Like
everything, this may lead to corner cases being wrong, but that's life, it will
also lead to the data being right for most users.
9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections,
should cover most OpenBSD L1 variants at least.
10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo,
but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD
sleeps are now running before sysctl if CPU data feature is required.
11. Too many to remember, but lots of subtle message output changes to make more
clear, more accurate, shorter, whatever.
12. USB: a very subtle fix, some devices can be both audio and video, like
cameras, but inxi would default to the first detected. Now it checks for both
before going to the list of checks, and correctly assigns a type that is both
audio and video to the audio and video hashes so both features will show the USB
device, not just Audio.
13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status
string, like 'no network' to 'no', which is silly. Now shows full string.
14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data
was still there with usbdevs but it required an extra -v, like: usbdevs -vv to
trigger, so now the OpenBSD USB ports works fine again.
15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils
package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping
up with that stuff!
16. OpenBSD SMART: the actual device being queried turns out to the 'c'
partition, the one that represents the entire disk, NOT the main device ID, like
sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So
previously SMART report would never have worked in OpenBSD.
17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid
if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote
fs mounts etc. This cleans up output, since these file system types will never
have labels or uuids.
18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with
Perl 5.008, and I realized I'd slipped up and had used the -k option without
testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns
on -k automatically, so the easy solution was just to remove the -k and leave
the -nnv, which is the same thing, but does not cause errors in early lspci.
There are also errors with reading as root some /sys uevent files, but upon
examination, those had only root write permission, so the perl -r test isn't
right. Don't think that can be fixed. See Can't/Won't fix for more.
Another issue I noticed was that in some cases Perl seemed to lose track of some
hash values in local %trigger in OptionsHandler, and just lose them, thus
leading to things like --help --version --recommends not working. Moving
%trigger to globals %show and %use fixed that one, but that's weird, no idea
what happened, but it works now.
Tested in Sarge 3.1, where core modules have to be explicitly installed, they
were not included in base Perl install. Kernel 2.4 had some key differences,
different lspci syntax, different /proc/partitions, so the block device output
and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005!
But these issues will not be corrected, kernel 2.24 is just too old, lol.
inxi should always run ok in very old systems, like Etch, back to when Perl 5.8
was standard, so bugs like this are always welcome, it's easy to slip up and use
something that didn't work in those old systems, then forget to test.
19. Corner case SMART errors, sometimes occur much later in output than inxi
expects, this is now corrected and errors should show in smart data no matter
where the main error type occured.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6,
assuming models 10, 11, are the same, which they should be since 12 is the same
as in family 4.
2. IPMI Sensors: More sensor syntax detections, sensors will never be stable...
3. OpenBSD: Rolled out live battery state feature, they have very good data,
simple, but solid, that allows for a quality battery state report. Handles both
Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah >
Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux
battery data has the same issue, though I think in most cases, the data is in
Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to
determine Ah may actually be slightly lower than the listed design voltage,
which inxi calls min: but it's actually the design voltage.
Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate
any samples, so can't say, if you have a NetBSD laptop that correctly reports
battery state in sysctl -a, please file an issue with some sample battery
charge/voltage syntax and values, ideally from > 1 system. If the data is
complete, it's easy to add support.
4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev
version data. Note that this is not guaranteed to be right, because USB devices
can be different rev versions than the speed they run at, but as far as I could
find, the USB revision data is not available in any practical sense, unless I
create a complicated recursive tool to build up a snapshot of the usb system and
devices from dmesg data, but I already blew a day on that attempt, so will wait
for more complete data in the usb tools in future. The rev version is based on
the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps
device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0
device, but a slow speed one.
4b. USB Type: Expanded fallback USB device type tests, these are useful for
cases where it's either a vendor defined type, or for Open/NetBSD, which do not
yet show USB class/subclass data. But it's a good fallback tool, added Mass
Storage, expanded detections.
5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data.
Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data,
problem with vm testing is no sensors, but don't have any NetBSD hardware
installs to verify. Stan gave it a good try, but could not get NetBSD running so
far, maybe later.
This basically means the -B and -s features are largely feature complete for the
BSDs as far as practical, though due to difficulties in getting the data in a
consistent clear way, some more advanced features, like gpu temps, which are now
available in Linux kernel values and lm-sensors, do not yet appear to be present
in the BSDs, though if this changes, the structures are in place to make
updates to these logics very easy to implement now.
Note that the --sensors-include and --sensors-exclude items, or config items,
work fine with this BSD logic, though you have to figure out what exact syntax
to use, but that's the same in Linux.
6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway,
they did a really good job, and the OpenBSD Perl packager made a very nice Perl
modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi
needs to run its features!!
So far OpenBSD only, but Pledge seems like a really good idea, so I figured,
let's give it a spin, even if it will only currently work on OpenBSD, but that's
fine, inxi is pledged as tightly as I could make it, including unpledging
features not required post options processing, once inxi knows what it's
actually going to be doing.
Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due
to never really being sure about what files inxi will need to be looking at
until well into the logic. I may look at that in the future.
7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent
Bluetooth hci report on Linux, added in one last fallback, rfkill state, which
allows inxi to always fallback to at least that basic data. Also added in which
tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so
on.
Also integrated into -xxx data, or for down state, the full rfkill report, since
that can be quite useful.
Note that bluetooth is a real pain for users to debug because you can have:
* Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped *
bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop *
rfkill: software: block/unblock; hardware: block/unblock - however, for
hardware, that means a physical button has been pressed to disable it, on the
laptop that is.
To make matters worse, one tool does not always even know when another tool has
changed something, for example, if I rfkill blocked hci0, then unblocked it,
hciconfig would keep seeing it as down until it was switched to on with
hciconfig explicitly. This is I suspect one reason hciconfig is being dropped,
it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter,
or rfkill.
8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root),
more consistent physical block size data, more reliable disk data, and for
-Dxxx, duid, if available. Also added disk partition table scheme, aka MBR /
GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART
fix for OpenBSD.
9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted
partitions report.
10. OpenBSD: added in CPU MT detections using siblings data, I think only
OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get
physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of.
11. OpenBSD: added in cpu speed min/max data, that was available in most cases,
didn't realize that.
12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for
example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires
root since that data is coming from dmidecode.
This logic update made BSD L-cache data much more reliable and consistent, and,
important, easy to work with. This was directly connected to Code Changes 2 and
3, which made dealing with those data sources a lot easier.
Note that L1/L2 cache data if not from OpenBSD will show note: check because
it's not possible to determine if it's a multithreaded MT cpu or not, and thus
if L1/L2 * core count would so often be totally wrong that inxi won't try to
guess, it will just list the single value found, and tell the user to check it
themselves.
13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that
replaces the fallback default used before, /etc/rc.d.
14. RAM Vendor: Issue #245 raised the point that it would be good to try to show
RAM vendor data when the manufactorer field is empty, and since that logic is
already present in disk_vendor, it was just matter of researching the product
IDs to find the matching patterns for the RAM vendors, the initial list is
pretty good, but will need updates now and then to correct errors. Also will
override only vendor ID 4 character hex value and see if it can find a better
value.
15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately).
The data is often, but sadly not always, available. I'm not clear why sometimes
it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root
user, which then blocks dmidecode, this is the only practical way to give basic
RAM data for OpenBSD, so that's running fine now, when the data is available,
with the added bonus of not needing doas/root.
Note that due to the way that this data is present, I can have inxi deduce some
things like how many arrays there are, and then guess at overall capacity, max
stick size, and so on, but all Array-x: values are followed by note: est because
they are never based on hard data, just extrapolations. I debated if inxi should
even show the guesses, but I think by saying note: est after each Array-x: item,
it's pretty clear that it's not hard data, and it does give an idea roughly. I
made an initial guess at > 1 ram array but found no data samples to let me see
if my guess was right or not, so > 1 array remains roughly theoretical until
shown to work or not work empirically.
While NetBSD sometimes has the system ram data in a similar way that OpenBSD
does in dmesg.boot, it varies too much, and is too inconsistent. There are not
enough data samples with good consistent data, and the samples I did see
suggested that it would take too much code and convoluted logic to handle the
variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block
/dev/mem so dmidecode should work fine.
16. Using system clang version info for OpenBSD kernel compiler, the assumption
being that a BSD is an OS, so the Clang version it shipped with would be the
clang version that compiled the kernel. Please correct if this is wrong.
17. OpenBSD RAID: support added for softraid, including for drive storage
totals, unmounted raid component detections. Plugged in pretty smoothly, able to
generate a partial report for non root, and shows message if not root.
18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm,
hyper-v, kvm. Not all of these would have been detected before. Also cleaned up
vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the
first found item.
19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID
matches!! Yep. What else can I say? Eternity? Man's quest for something that
cannot be found, yet these strivings never cease, here manifested by always new
vendors and ID matches!
--------------------------------------------------------------------------------
DOCUMENTATION:
1. Very significant ongoing upgrades to the docs in inxi-perl/docs/,
particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These
are now increasingly useful, and I am trying to keep in particular
inxi-values.txt up to date as a primary reference for various features, though
it will always lag, because that's how it is, lol.
2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered
lists and headers consistent, but otherwise did not change any of the actual
content.
--------------------------------------------------------------------------------
CODE CHANGES:
1. Complete rewrite of BSD disk/partition data tools, now there is one core
tool that generates a mega-disk/partition hash, which is then used for all
features that need partition/disk data. This worked out super well, and allowed
new features like BSD Unmounted disk data to be generated for the first time
ever, along with filling in various block device fields that were missing
before.
2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which
allowed for much more granular data generation, along with a complex %dboot hash
which stores all sub types as well as the main full dataset. This allowed inxi
to stop looping through all of dmesg data each time a feature needed it. Now all
the data types are assigned if required by a feature, and only then. This, along
with change 1, worked really well.
See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live
data were / are merged, the result is far more robust now, and far less prone to
error.
3. Similar to dmesg changes, used same methods for sysctl data, now all the data
is assigned to %sysctl data structure based on if needed or not, so it only does
the assignments one time, in one location. Much cleaner code this way, and
allows for testing set/unset substructures, like $sysctl{'cpu'}.
4. The %dboot and %sysctl refactors went so well that I switched the core USB
and Devices to also use %usb and %devices structures. These updates let me dump
a lot of global hashes and arrays, and leaned everything down a lot, and also
removed basically all the testing loops for these data types, now the Item
features just test to see if a reference to the specific type exists, if it
does, it has data, if not, it doesn't, this is a lot easier to manage.
5. Ongoing: moving related subroutines to Packages, the goal is to have pretty
much all related subroutines (functions) contained in parent classes/packages,
makes it easier to maintain.
6. Ongoing: making all internal package tools have similar sub names, getting
rid of the specific names for output and data generator functions. This makes
each Item Generator increasingly like all the others, as much as practical.
7. A big one, renamed all the feature generators to be XxxxxItem, instead of
XxxxData, which was colliding as a package name with actual data generator
tools, now all the Feature generators are [Feature]Item, and all the Data
generators have Data type names where relevant. This avoided in particular the
silly case where I was relying on case to differentiate UsbData and USBData,
feature vs data generator.
8. As part of the move to data hash global structures, also moved as many of the
top global scalars and hashes and arrays to these now much more heavily utilized
global hashes, like %alerts, %use, %fake, %force, and so on. There are now far
fewer globals running than before, and where it makes sense, I keep moving them
into global hashes, and giving the global hashes more work to do.
9. Significantly expanded list of debuggers for specific data types always
available, see docs/inxi-values.txt for list of options there. Decided for rapid
development, it was too much of a pain to always be uncommenting the debuggers,
so now am uncommenting, adding to @dbg supported items, then documenting. I
guess this means the @dbg items are more or less stable and consistent now, give
or take.
10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much
more robust and to rely less on very fragile regex parsing patterns, takes more
lines of code, but better than having the detections break every other BSD
release. This was part of the %device and %usb refactors as well.
11. Fixed system_files() too, which was really silly logic, it used a global
packed hash of system files, then would do a function call for the paths when
required, which was redundant since the values were already in a hash which
could be used directly. This was a throwback to inxi gawk/bash, where hashes
were not really used in this way, and the logic had been translated to Perl
without thinking about it, but once I thought about it, I realized how silly
that was. This must have knocked off a good 50 or more unnecessary, and always
expensive, function calls.
2021-04-17 03:41:58 +00:00
|
|
|
And of course, a big thanks to locsmif, who figured out a lot of the core
|
|
|
|
|
ideas, logic, and tricks originally used in inxi Gawk/Bash.
|
Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!!
raspberry pi!! New Features!!! Enhanced old features!!! Did I
mention bluetooth?! USB? Audio? No? well, all hugely upgraded!
------------------------------------------------------------------------
BUGS:
1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger,
resulted in hardcoded kernel compiler version always showing.
Note that there is a new inxi-perl/docs/inxi-bugs.txt file to
track such bugs, and matched to specific tagged releases so you
know the line number and items to update to fix it.
2. Typo in manjaro system base match resulted in failing to report
system base as expected.
------------------------------------------------------------------------
KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED:
1. OpenBSD made fvwm -version output an error along with the
version, and not in the normal format for standard fvwm, this
is just too complicated to work around for now, though it could
be in theory by creating a dedicated fvwm-oBSD item in
program_values. But that kind of granularity gets too hard to track,
and they are likely to change or fix this in the future anyway.
Best is they just restore default -version output to what it is
elsewhere, not nested in error outputs.
2. Discovered an oddity, don't know how widespread this
is, but Intel SSDs take about 200 milliseconds to get the sys
hwmon based drive temps, when it should take under a
millisecond, this may be a similar cause as those drives having
a noticeable SMART report delay, not sure. This is quite
noticeable since 200 ms is about 15% of the total execution
time on my test system.
------------------------------------------------------------------------
FIXES:
1. For --recommends, added different rpm SUSE xdpyinfo package name.
2. Distro Data: added double term filter for lsb-release due to sometimes
generating repeated names in distro.
3. Packages: fix for appimage package counts.
4. Desktop: fixed ID for some wm when no xprop installed, fallback to
using @ps_cmd detections, which usually work fine.
5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB.
5b. If no swap devices found, BSDs were not correctly showing
no swap data found message. Corrected.
6a. Bluetooth: Removed hcidump from debugger, in some cases, that will
just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger
data collection with @ps_cmd bluetooth running test. Only run if
bluetooth service is running.
6b. Bluetooth: running detections have to be very strict, only
bluetoothd, not bluetooth, the latter can show true when bluetoothd
is not running, and did in my tests.
7. USB: with Code Change 1, found a few places where fallback usb type
detections were creating false matches, which resulted in say,
bluetooth devices showing up as network devices due to the presence
of the word 'wireless' in the device description. These matches are
all updated and revised to be more accurate and less error prone.
8. Battery: an oversight, had forgotten to have percent used of
available capacity, which made Battery data hard to decipher, now
it shows the percent of available total, as well as the condition
percent, so it's easier to understand the data now, and hopefully
more clear.
9a. OpenBSD changed usbdevs output format sometime in the latest
releases, which made the delicate matching patterns fail. Updated
to handle both variants. They also changed pcidump -v formatting
at some point, now inxi will try to handle either. Note that
usbdevs updates also work fine on NetBSD.
9b. FreeBSD also changed their pciconf output in beta 13.0, which
also broke the detections completely, now checks for old and new
formats. Sigh. It should not take this much work to parse tools
whose output should be consistent and reliable. Luckily I ran
the beta prior to this release, or all pci device detections
would simply have failed, without fallback.
9c. Dragonfly BSD also changed an output format, in vmstat, that
made the RAM used report fail. Since it's clearly not predictable
which BSD will change support for which vmstat options, now just
running vmstat without options, and then using processing logic
to determine what to do with the results.
10. It turns out NetBSD is using /proc/meminfo, who would have
thought? for memory data, but they use it in a weird way that
could result in either negative or near 0 ram used. Added in
some filters to not allow such values to print, now it tries
to make an educated guess about how much ram the system is
really using based on some tests.
11. Something you'd only notice if testing a lot, uptime failed
when the uptime was < 1 minute, it had failed to handle the seconds
only option, now it does, seconds, minutes, hours:minutes,
days hours:minutes, all work.
12. Missed linsysfs type to exclude in partitons, that was a partner
to linprocfs type, both are BSD types.
13. Added -ww to ps arguments, that stops the cutting width to terminal
size default behavior in BSDs, an easy fix, wish I'd known about
that a long time ago.
15. gpart seems to show sizes in bytes, not the expected KiB, so
that's now handled internally. Hopefully that odd behavior won't
randomly change in the future, sigh.
16. Fixed slim dm detection, saw instance where it's got slim.pid
like normal dms, not the slim.lock which inxi was looking for, so
now inxi looks for both, and we're all happy!
------------------------------------------------------------------------
ENHANCEMENTS:
1. Added in something that should have been there all along, now inxi
validates the man page download as well as the self, this avoids
corrupted downloads breaking the man.
2. Init: added support for shepherd init system.
3. Distro Data: added support for guix distro ID; added support for
NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main
package version for the distro version ID, which isn't quite the
same as the version you download, but it's close. Also added os-release
support for BSDs, using similar tests as for linux distros, that
results in nicer outputs for example for Dragonfly BSD.
4. Package Data: added guix/scratch [venom]/kiss/nix package managers.
Update for slackware 15 package manager data directory relocation,
now handles either legacy current or future one.
5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD
pkg repos.
6. USB Data: added usbconfig. That's FreeBSD's, and related systems.
7. Device Data: Added pcictl support, that's NetBSD's, I thought
inxi had supported that, but then I remembered last time I tried to
run netBSD in a vm, I couldn't get it figured out. Now debugged and
working reasonably well.
8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device,
which is on a special mmcnr type, now works, that stopped working in
pi 3, due to the change, now it's handled cleanly. Also added support
for pi bluetooth, which lives on a special serial bus, not usb.
For Raspberry Pi OS, added system base detections, which are tricky.
Also matched mmcnr devices to IF data, which was trickyy as well.
Note that as far as I could discover, only pi puts wifi on mmcnr.
9. Bluetooth: due to deprecated nature of the fine hciconfig
utility, added in support for bt-adapter, which also allows matching
of bluetooth data to device data, but is very sparse in info
supplied compared to hciconfig. bluetoothctl does not have enough
data to show the hci device, so it's not used, since inxi can't
match the bluetooth data to the device (no hci[x]). This should help
the distros that are moving away from hciconfig, in particular,
AUR is only way arch users can get hciconfig, which isn't ideal.
10. New tool and feature, ServiceData, this does two things,
as cross platform as practical, show status of bluetooth service,
this should help a lot in support people debugging bluetooth problems,
since you have bluetooth enabled but down, or up, disabled, and you
can also have the device itself down or up, so now it shows all that
data together for when it's down, but when the device is up, it just
shows the device status since the other stuff is redundant then.
In -Sa, it now shows the OS service manager that inxi detected
using a bunch of fallback tests, that's useful to admins who
are on a machine they don't know, then you can see the service
manager to use, like rc-service, systemctl, service, sv, etc.
11. Big update for -A: Sound Servers: had always been really
just only ALSA, now it shows all detected sound servers, and whether
they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio,
sndio, JACK. Note that OSS version is a guess, might be wrong source
for the version info.
12. Added USB device 'power:' item, that's in mA, not a terrible
thing to have listed, -xxx. This new feature was launched cross
platform, which is nice. Whether the BSD detections will break
in the future of course depends on whether they change the output
formats again or not. Also added in USB more chip IDs, which can
be useful. For BSDs, also added in a synthetic USB rev, taken
from the device/hub speeds. Yes, I know, USB 2 can have low speed,
full speed, or high speed, and 1.1 can have low and full speeds,
so you actually can't tell the USB revision version from the speeds,
but it's close enough.
13. Made all USB/Device data the same syntax and order, more
predictable, bus, chip, class IDs all the same now.
14. Added in support for hammer and null/nullfs file system types,
which trigger 'logical:' type device in partitions, that's also
more correct than the source: Err-102 that used to show, which
was really just a flag to alert me visibly that the partition
type detection had simply failed internally. Now for detected
types, like zfs tank/name or null/nullfs, it knows they are
logical structures.
15. Expanded BSD CPU data, where available, now can show L1/L2/
L3 cache, cpu arch, stepping, family/model ids, etc, which is
kind of nifty, although, again, delicate fragile rules that
will probably break in the future, but easier to fix now.
16. By an old request, added full native BSD doas support.
That's a nice little tool, and it plugged in fairly seamlessly
to existing sudo support. Both the internal doas/sudo stuff
should work the same, and the detection of sudo/doas start
should work the same too.
17a. Shell/Parent Data: Big refactor of the shell start/parent logic,
into ShellData which helped resolve some issues with running-in
showing shell name, not vt terminal or program name. Cause of that
is lots of levels of parents before inxi could reach the actual
program that was running inxi. Solution was to change to a longer
loop, and let it iterate 8 times, until it finds something that is
not a shell or sudo/doas/su type parent, this seems to work quite
well, you can only make it fail now if you actually try to do it on
purpose, which is fine.
This was very old logic, and carried some mistakes and
redundancies that made it very hard to understand, that's cleaned
up now. Also restored the old (login) value, which shows
when you use your normal login account on console, some system
will also now show (sudo,login) if the login user sudos inxi,
but that varies system to system.
17b. BSD running-in: Some of the BSDs now support the -f flag
for ps, which made the parent logic for running-in possible for
BSDs, which was nice. Some still don't support it, like OpenBSD
and NetBSD, but that's fine, inxi tests, and if no support detected,
just shows tty number. Adding in more robust support here cleaned
up some redundant logic internally as well.
17c. Updated terminal and shell ID detections, there's quite a few
new terminals this year, and a new shell or two. Those are needed
for more reliable detections of when the parent is NOT a shell,
which is how we find what it is.
18. Added ctwm wm support, that's the new default for NetBSD,
based on twm, has version numbers.
19. Upgraded BSD support for gpart and glabel data, now should
catch more more often.
20. For things like zfs raid, added component size, that doesn't
always work due to how zfs refers to its components, but it often
does, which is better than never before.
21. To make BSD support smoother, got rid of some OpenBSD only
rules, which in fact often apply to NetBSD as well. That may
lead to some glitches, but overall it's better to totally stay
away from OpenBSD only tests, and all BSD variant tests, and
just do dynamic testing that will work when it applies, and
not when it doesn't. In this case, added ftp downloader support
for netBSD by removing the openBSD only flag for that item.
There's a bit of a risk there in a sense since if different ftp
programs with different options were to be the fallback for something
else, it might get used, but that's fine, it's a corner case, better
to have them all work now than to worry about weird future things.
But limiting it to only BSDs should get rid of most of the problem.
vmstat and optical drive still use net/openbsd specifics because
it is too tricky to figure out it out in any more dynamic way.
22. For -Sxxx, added if systemd, display, virtual terminal number.
Could be useful to debug subtle issues, if the user is for example
not running their desktop in vt 7, the default for most systems.
------------------------------------------------------------------------
CHANGES:
1. Moved battery voltage to -Bx output, the voltage is quite
important to know since that is the key indicator of battery state.
If voltage is within .5 volts of specified minimum, shows voltage
for -B since that's a prefail condition, it's getting close to
death.
2. In partitions and raid, when the device was linear raid logical
type layout, it said, no-raid, when it should be 'linear', that's
now cleaner and more correct.
3. When running-in is a tty value, it will now show the entire
tty ID, minus the '/dev/tty', this will be more precise, and also
may resolve cases where tty was fully alpha, no numbers, previously
inxi filtered out everything that was not a number, but that can
in some tty types remove critical tty data, so now it will show:
running-in:
tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E];
tty rx [would have not shown at ll before]
------------------------------------------------------------------------
CODE CHANGES:
NOTE: unlike the previous refactors, a lot of these changes were
done to make inxi more maintainable, which means, slightly less
optimized, which has been my preference in the past, but if the
stuff can't be maintained, it doesn't matter how fast it runs!
These changes have really enhanced the quality of the code and
made it a lot easier to work with. It's also now a lot easier to
add debuggers, force/fake data switches, etc, so it gets done,
unlike before, when it was a pain, so it got skipped, and then
caused bugs because of stray debuggers left in place, and so on.
The bright side is while reading up on this, I learned that using
very large subs is much more efficient than many small ones,
which I've always felt was the case, and it is, so the style
used internally in inxi proves to be the best one for optimizations.
These refactors, ongoing, have now touched at least 1/3, almost
1/2, of the entire inxi codebase, so the stuff is getting more
and more consistent and up to date, but given how old the logic
is in places, there will be more refactors in the future, and
maybe once the code is easier to maintain, some renewed
optimizations!, if we can find anything that makes sense, like
passing array/hash references back to the caller, already the
first half is done, passing references to the sub/method always.
The second part is started, using the Benchmark Perl module,
which really speeds up testing and helps avoid pointless tweaks
that do little re speed improvements.
I could see with some care some areas where working on data
directly via references could really speed things up, but it's
hard to write and read that type of code, but it's already being
done in the recursive data and output logics, and a few other
places.
1. Large refactor of USBData, that was done in part to help make
it work for BSDs better, but also to get it better organized.
This refactor also made all the device items, like -A,-G,-N,-E
use the same methods for creating USB output, previously they
had used a hodgepodge of methods, some super old, it was not
possible to add USB support more extensively for BSDs without
this change.
Also added in some fallback usb type detection tools using
several large online collections of that info to see what possible
matching patterns could catch more devices and correctly match
them to their type, which is the primary way now that usb output
per type is created. This really helps with BSDs, though BSD
usb utilities suffer from less data than lsusb so they don't always
get device name strings in a form where they can be readily ID'ed,
but it's way better than it was before, so that's fine!
Moved all previous methods of detecting if a card/device was USB
into USBData itself so it would all be in one place, and easier
to maintain.
All USB tools now use bus_id_alpha for sorting, and all now
sort as well, that was an oversight, previously the BSD usb
tools were not sorted, but those have been enhanced a lot, so
sorting on alpha synthetic bus ids became possible.
Removed lsusb as a BSD option, it's really unreliable, and the data
is different, and also varies a lot, it didn't really work at all
in Dragonfly, or had strange output, so lsusb is now a linux only
item.
2. Moved various booleans that were global to %force, %loaded, and
some to the already present, but lightly used, %use hashes. It was
getting too hard to add tests etc, which was causing bugs to happen.
Yes, using hashes is slower than hardcoding in the boolean scalars,
but this change was done to improve maintainability, which is starting
to matter more.
3. Moved several sets of subs to new packages, again, to help with
debugging and maintainability. MemoryData, redone in part to
handle the oddities with NetBSD reporting of free, cached, and
buffers, but really just to make it easier to work with overall.
Also moved kernel parameter logic to KernelParameters, gpart logic
to GpartData, glabel logic to GlabelData, ip data IpData, check_tools
to CheckTools, which was also enhanced largely, and simplified,
making it much easier to work with.
4. Wrapped more debugger logic in $fake{data} logic, that makes
it harder to leave a debugger uncommented, now to run it, you have
to trigger it with $fake{item} so the test runs, that way even if
I forget to comment it out, it won't run for regular user.
5. Big update to docs in branch inxi-perl/docs, those are now
much more usable for development. Updated in particular
inxi-values.txt to be primary reference doc for $fake, $dbg,
%force, %use, etc types and values. Also updated inxi-optimization.txt
and inxi-resources.txt to bring them closer to the present.
Created inxi-bugs.txt as well, which will help to know which known
bugs belonged to which frozen pools. These bugs will only refer
to bugs known to exist in tagged releases in frozen pool distros.
6. For sizes, moved most of the sizing to use main::translate_size,
this is more predictable, though as noted, these types of
changes make inxi a bit slower since it moved stuff out of inline
to using quick expensive sub calls, but it's a lot easier to
maintain, and that's getting to be more important to me now.
7. In order to catch live events, added in dmesg to dmesg.boot data
in BSDs, that's the only way I could find to readily detect
usb flash drives that were plugged in after boot. Another hack,
these will all come back to bite me, but that's fine, the base
is easier to work on and debug now, so if I want to spend time
revisiting the next major version BSD releases, it will be easier
to resolve the next sets of failures.
8. A big change, I learned about the non greedy operator for
regex patterns, ?, as in, .*?(next match rule), it will now
go up only to the next match rule. Not knowing this simple
little thing made inxi use some really convoluted regex to
avoid such greedy patterns. Still some gotchas with ?, like
it ignores following rules that are zero or 1, ? type, and
just treats it as zero instances. But that's easy to work with.
9. Not totally done, but now moved more to having set data
tools set their $loaded{item} value in get data, not externally,
that makes it easier to track the stuff. Only where it makes
sense, but there's a lot of those set/get items, they should
probably all become package/classes, with set/get I think.
10. Optimized reader() and grabber() and set_ps_aux_data(), all
switched from using grep/map to using for loops, that means
inxi doesn't have to go through each array 2x anymore, actually
4x in the case of set_ps_aux_data(). This saved a visible
amount of execution time, I noticed this lag when running
pinxi through NYTProf optimizer, there was a quite visible
time difference between grabber/reader and the subshell
time, these optimizations almost removed that difference,
meaning only the subshell now really takes any time to run.
Optimized url_cleaner and data_cleaner in RepoData, those
now just work directy on the array references, no returns.
Ran some more optimization tests, but will probably hold off
on some of them, for example, using cleaner() by reference is
about 50% faster than by copy, but redoing that requires
adding in many copies from read only things like $1, so
the change would lead to slightly less clean code, but may
revisit this in the future, we'll see.
But in theory, basically all the core internal tools that
take a value and modify it should do that by reference
purely since it's way faster, up to 10x.
2021-03-16 01:44:00 +00:00
|
|
|
|
|
|
|
|
.\" EOF
|
